Document your stuff

Reverse interview, entrevistar al entrevistador, y ver si ellos son un fit para uno. Un par de buenos recursos, y mis preguntas favoritas:

• What has been a challenge for this job in the past?
• Why are you looking to fill this role
• What is the most important impact I can make in the 90 days
• What are major trends affecting the company in the next year or two
• What makes someone successful is there something I should do to be successful from day one?
• What have you learned or how have you changed since working here?
• What problem could I tackle for you quickly in this job?
• Based on the interview, what feedback do you have for me?
• What’s the employee turnover?
• What's the on-call plan/schedule?
• What does the onboarding look like?
• How do you test code?
• How do you integrate and deploy changes? Is it CI/CD?
• How quickly can you setup a new local test environment for the product?
• What happens when the team misses a release target?
• How’s the engineering culture?
• What’s the current tech stack?
• Where is the engineering team located? It is fully remote?
• How big is the team?
• Do you have any concerns about my experience or skill set?
• When was the last time you took time off? Whats the expectation when youre on vacations? expected that employees be checking emails, slack messages, etc. when OOO.

Fuentes:

• Reverse interview
• Questions I'm asking in interviews

TIL que los elementos input cuando reciben el valor de search para atributo type, nos proveen funcionalidades como autocomplete y una manera nativa de limpiar el input.

<form>
    <div>
        <input type="search" id="mySearch" name="q">
        <button>Search</button>
    </div>
</form>

Funciona similar al atributo text, pero dependiendo del browser el estilo es diferente, en Chrome muestra una X que cuando se le da click limpia el input.

Referencia: MDN <input type="search">

TIL el objeto String tiene un método repeat()

The repeat() method constructs and returns a new string which contains the specified number of copies of the string on which it was called, concatenated together.

String.prototype.repeat()

Encontré el canal de Youtube TechWorld with Nana y me ha ayudado a refrescar conceptos de DevOps, algunos de los que he visto en las ültimas semanas:

• GitHub Actions Tutorial - Basic Concepts and CI/CD Pipeline with Docker
• Docker Tutorial for Beginners [FULL COURSE in 3 Hours]
• What is GitOps, How GitOps works and Why it's so useful
• ArgoCD Tutorial for Beginners | GitOps CD for Kubernetes

Estoy trabajando en un proyecto en el que hacer prop drilling ya se esta saliendo de control, algunas notas y links que me estan ayudando a tomar una decisión sobre como resolver el problema de state management.

State Management In Next.js: alto nivel, sirve como introducción; al final NextJS es un framework y no incluye nada que nos permita manejar el estado de la aplicacion, algunas alternativas que mencionan: prop drilling, usar Context API, Jotai. Me gusto como resume las consideraciones de client-side fetching:

When requesting data from the client-side, it is important to be mindful of a few things:

• the user’s network connection: avoid re-fetching data that is already available
• what to do while waiting for the server response
• how to handle when data is not available (server error, or no data)
• how to recover if integration breaks (endpoint unavailable, resource changed, etc)

Blogged Answers: Why React Context is Not a "State Management" Tool (and Why It Doesn't Replace Redux) incluye algunos buenos puntos sobre Context y Redux, que son, como se diferencia y cuando usarlos.

Comparing Context and Redux

• Context

  • Does not store or "manage" anything
  • Only works in React components
  • Passes down a single value, which could be anything (primitive, objects, classes, etc)
  • Allows reading that single value
  • Can be used to avoid prop-drilling
  • Does show the current context value for both Provider and Consumer components in the React DevTools but does not show any history of how that value changed over time
  • Updates consuming components when the context value changes, but with no way to skip updates
  • Does not include any mechanism for side effects - it's purely for rendering components

• React+Redux

  • Stores and manages a single value (which is typically an object)
  • Works with any UI, including outside of React components
  • Allows reading that single value
  • Can be used to avoid prop-drilling
  • Can update the value via dispatching an action and running reducers
  • Has DevTools that show the history of all dispatched actions and state changes over time
  • Uses middleware to allow app code to trigger side effects
  • Allows components to subscribe to store updates, extract specific pieces of the store state, and only re-render when those values change

  Me gusto mucho esta parte sobre entender las herramientas

In order to use any tool correctly, it's critical to understand:

• What its purpose is
• What problems it's trying to solve
• When and why it was originally created

It's also critical to understand what problems you are trying to solve in your own application right now, and pick the tools that solve your problem the best - not because someone else said you should use them, not because they’re popular, but because this is what works best for you in this particular situation.

Por fin me anime, e inicie con Epic React de Kent C. Dodds; siguiendo con los consejos de Kent, voy a empezar a tomar notas sobre los conceptos aprendidos, estas son del primer curso, React Fundamentals.

Imperative vs Declarative

The imperative approach is concerned with HOW you’re actually going to get [a seat]. You need to list out the steps to be able to show HOW you’re going to get [a table]. The declarative approach is more concerned with WHAT you want, [a table for two].

• Imperativo: cuando declaramos instrucciones especificas, casi paso a paso, que van definiendo como vamos a obtener algo.
• Declarativo: programación funcional.

Lectura recomendada:

• JavaScript modules - MDN

• Imperative vs Declarative Programming

  JSX

  Para ver como JSX se compila a JavaScript se puede usar el REPL de Babel, sirve mucho para terminar de entender lo que pasa cuando usamos JSX.

Posiblemente la definición más sencilla de qué es un componente:

Components are basically functions which return something that is “renderable” (more React elements, strings, null, numbers, etc.)

Lectura recomendada:

• What is JSX?
• JSX In Depth