Jumping straight ahead to our IDE in order to shoot some code might feel creative but isn’t that effective. When building web applications that solve actual and not imaginary problems we need to think as a user first and define all the paths and flows we should follow to fulfill our goal.

Engineers should not be afraid of change. Actually they should learn how to embrace it by sharpening their skillset constantly. This involves also the soft skills apart from the hard ones.

What is the key ingredient for a brand new company?

Having multiple major versions of a package in a project might sound a little tricky but it is definitely doable.

React 17 is getting closer without actually adding any fancy new features. Its purpose is to make gradual upgrades possible by letting us use multiple React versions in one application.

In this blog post we are going to discuss about the little things that play a vital role in engineers success and have nothing to do with actual coding.

Every now and then, I come across mentally exhausted and frustrated web developers who try to test their work by clicking here and there in the UI. Most of the times something is still missing so they have to repeat this routine yet another time. My proposal is to simply turn off the browser.

Every now and then, I come across mentally exhausted and frustrated web developers who try to test their work by clicking here and there in the UI. Most of the times something is still missing so they have to repeat this routine yet another time. My proposal is to simply turn off the browser.

Every now and then, I come across mentally exhausted and frustrated web developers who try to test their work by clicking here and there in the UI. Most of the times something is still missing so they have to repeat this routine yet another time. My proposal is to simply turn off the browser.

Every now and then, I come across mentally exhausted and frustrated web developers who try to test their work by clicking here and there in the UI. Most of the times something is still missing so they have to repeat this routine yet another time. My proposal is to simply turn off the browser.

Many developers share proudly their contributions graph throughout social networks or CVs to demonstrate how hard they have been working which is amazing and speak volumes for their work-ethic. The thing is that this does not tell us actually the full story.

We live in the seniors era. Suddenly everyone should be a senior so others can take him seriously. This is totally wrong for so many reasons

RecoilJS is an experimental state management library for React that works and thinks like it. It aims to solve common issues like state interdependencies among related components, unwanted re-renderings across complex components trees, cross-app observations and many more.

TypeScript is meant to make JavaScript stronger and safer by helping us stay type-safe while using it. Using any defeats this purpose and can easily become the root evil the more we keep on using it.

Many React engineers are really uninterested or even sloppy when it comes about naming their components. This might be totally fine at first, but it can turn out to be an awful strategy as the application's codebase gets bigger.

Managing environment variables in a secure and easy way is a crucial process for any robust and mature web application. In a Sapper application we need to put some key pieces together in order to make things work.

Many frontend developers who use modern React, wonder why their components render twice during development but this is actually happening for a good reason.

For years we couldn't replace all instances of a substring in a string without the use of a global regexp. This is the issue that String.prototype.replaceAll is going to solve.

React Fast Refresh is the successor of React Hot Loader. It was initially released for React Native and soon it will be included in Create React App as an experimental feature.

When we need to know whether at least 1 promise got resolved among an iterable of Promise objects, Promise.any() is the solution we are asking for.

Many times we try to launch an application locally and we face an annoying error saying this port is already in use. How can we tackle this fast?

Accessing global object across different environments has been a challenging task for many years in the JavaScript community. This is exactly what globalThis is trying to tackle.

Accessing deep nested keys across objects has been a tricky procedure for JavaScript engineers since they should take care of non-existent keys down the road. Optional chaining and Nullish coalescing operators are meant to tackle this issue.

There are times we need to launch an HTTP server locally to test a Single Page Application, or a production bundle or even a static website. So how do we do this?

The most common use of refs in React is to create references to DOM elements and run imperative logic when needed. Force elements to become focused, scroll up and stuff like that. React hooks take all these a step further so we can use refs to store values we need to watch.

Vue 3 has introduced two primary methods to create reactive variables. These are ref and reactive methods. Because of them, we can leave behind the beloved data function we have been using in Vue 2 to declare local state across our components.

There are times when we need to know whether all promises we are running are done. This can be taken care of with Promise.allSettled().

It is pretty common to load server-side data in our UI components in order to present dynamic content. In Vue 2 we have been using mostly created lifecycle hook to accomplish this but in Vue 3 there is no need to do so since we can simplify things a bit due to setup method.