Neat features of Flow.

I recently took a couple hours to read through the Flow docs, which was an informative and valuable use of time. Here are a bunch of »

Jest + Chai and expect.assertions.

At Transparent Classroom, we use both Mocha/Chai to test our modules and Redux code and Jest to test our React components. Mocha/Chai and Jest »

Source maps for Sentry: setting the UTF-8 encoding.

We use Sentry at TransparentClassroom to monitor errors in our front-end application. It's an excellent tool and has proven very useful, but for the longest time »

Node: exploring asynchronous vs. multi-threaded approaches.

I recently ran a small exercise to demonstrate the power, limitations, and workarounds of Node. In the process, I gained a deeper understanding of asynchronous operations »

Gulp basics.

Gulp. Without understanding how it works, reading the file can make programmers perform its namesake. (Still, it's better than the equivalent for Grunt. Oh snap!) Gulp »

Travis CI and you.

Software projects are an iterative process. Tests, linting, and even deployment should occur at every step of that iteration. One can make such tasks much easier »

Environment variables.

Environment variables are essential in practically any web app. If you ever use an API where they give you unique credentials, you need them. If you »

Code coverage.

Writing tests are useful, but on large projects it can be easy to lose track of what portions have been tested. That is where the concept »

Dealing with failure.

Two weeks ago, I failed. It was not the light-weight kind of failure: the "oops, my bad, let's fix it, no big deal." This failure was »

My first open source feature contribution.

I am now designated as a collaborator on an open source project! It's for DocToc, a npm package with a noticeable userbase: ~900 downloads from npm »