I recently attended the Software Craftsmanship North America conference. Audrey Troutt gave a talk, Learn Better Together, that really caught my attention.

During the recent upgrade from Octopress 2 to Octopress 3, I temporarily lost all of the comments that people have left on posts. Here’s what I did to recover them.

React Native makes it very easy to include platform-specific code in a project. But what if we only need to customize a few styles?

When you work with open-source software, you sometimes need to deal with projects that have stalled. How do you handle it? What do you do?

Recently, we’ve been talking about encapsulating the Redux state tree. In the previous post, we looked at the asymmetry that arises between reducers and selectors when using combineReducers. We came up an approach that with works well when using a Rails-style project organization. But if we try to use it in a modular (domain-style) project structure, we run into issues.

In my previous post, I talked about using actions, reducers, and selectors to encapsulate the Redux state tree. In that post, I showed an approach that works great for a single top-level reducer, but doesn’t address how to handle decomposed reducers. Let’s talk about that.

In the next few days, I’ll be re-launching this blog on an upgraded blogging platform. I’ve done my best to keep all of the content and static page links the same. Please let me know if you notice anything broken.

In a Redux application, the bulk of the application’s data is stored as a “state tree” in a central location, the store. The shape and structure of the state tree has a large impact on the ease of development and performance of the application. It is often valuable to refactor the state tree over time to address issues. How do we do this safely?

Snapshot Testing has been getting a fair bit of attention recently with some new tool support that makes it easy to use. But is that a good thing?

In a JavaScript codebase of sufficient size, you’ll likely run into the need to import or require files from a different part of the codebase. Too much of this can be a sign of a system that isn’t structured very well, but even in a well-architected, modular codebase, there will be dependencies between the modules.