Improved Error Handling in React 16 with Error Boundaries
React 16 has entered the beta phase and with it comes with two of my favorite additions in a long time: returning arrays in the render() method and official support for error boundaries.
My ramblings on programming, product development, and more, collected in chronological order.
React 16 has entered the beta phase and with it comes with two of my favorite additions in a long time: returning arrays in the render() method and official support for error boundaries.
React testing (and JS testing, in general) is an incredibly broad topic with a lot of nuance. In this post, I primarily want to focus on exploring some of the basic what's and why's of, as well as a few best practices for, testing React applications.
This past weekend, I finally decided it was time to refresh things around here. Despite the fact that I still felt the old design looked pretty good, I didn't feel that the underlying technology and overall feel were particularly reflective of how I (or, increasingly, anyone) build sites these days.
I had the privilege of attending jsDay last week in Verona, Italy. One of my favorite talks during the two-day event was titled...
Lately I've found myself working with an ever increasing number of WordPress multisite installations, each built with a slightly different approach than the others. As a result, I've spent a lot of time thinking about how to architect these networks to maximize code clarity and maintainability.
In short, separation of concerns is a guiding principal in software development centered on the idea that programs should have distinct sections, with each section being responsible for its own concern.