Rationale When working in a React application, one pain point that often comes up is Redux. People say that as soon as an application uses it, things quickly get overrun with boilerplate and "wiring" code that ultimately clogs your codebase more than it helps it. This isn't something inherent to Redux but more something to do with the best practices associated with it, and with people...

Why Gatsby? One of the greatest aspects of modern web development is how modular and composable everything has become. Building an application these days has become a lot like tinkering with building blocks: piecing together packages, APIs, services and so on. Each doing what they do best. We've learned that reinventing the wheel is often not the solution and by embracing interoperability we've...

Why immutability? When working on a React application that needs to handle state, one of the main pitfalls to watch out for is accidental mutations. Which is fancy talk for mistakenly modifying stuff you didn't want to change: let user = { name: "foo" }; let updated = user; updated.name = "bar"; updated.name; // "bar" user.name; // "bar" In this case,...