The other day I was uploading a lot of content, including images, to a 3rd party service. I put together all my objects and mapped through them to fire off requests. Nearly immediately, I blew past the API rate limiter, and my requests started failing. Oops.

We've all been there: you’re multiple folders deep in a project, and you must reach up to grab a component in a top-level folder with an unknown level of ../'s to traverse.

These complications increase drastically as a project grows in size and complexity; they might even cause fear whenever the word "refactor" is uttered. Fear not! There is a solution to your woes—path aliases.

Most teams develop patterns or preferred ways of writing code, but it can be tedious to enforce adhering to those patterns, especially for new team members onboarding. To help this, we rely on linters for basic formatting, but did you know you can take preference-enforcement to the next level by writing your own lint rules?

Do you use switch/case statements or do you use object literals in your Javascript? 

Even though React's useReducer has gained a lot of popularity during the last couple of years, it can be difficult to use for some common cases. Specifically, it requires a lot of boilerplate to support async actions.

Declarative code: it’s a hot term in all types of programming. But what does it really mean? More importantly, how do you make the jump from understanding the concept to actually writing declarative code in your projects?