The publisher is using a new address for their RSS feed. Please update your feed reader to use this new URL:http://derickbailey.com/feed/

JavaScript moves fast. Both the language, and the frameworks and tooling around it are receiving updates at an enormous rate these days. This pace of change oftens means a project you worked on a few months ago is now using “outdated” tools and technologies compared to your current project. And the older a project gets, the more difficult it is...

JavaScript is anything but a “static” language (pun intended). It seems everything is changing – even the naming of releases has changed, with years marking the language version. And starting with the release of ES6 (officially, “ES2015”), the language has has continued to evolve at a rapid pace, introducing a staging system to mark the progress...

A while back I wrote a post about selecting a base Docker image for Node.js. In that post, I talked about the size difference of the default build for Node.js and the smaller, “slim” and “alpine” builds. The difference can be significant: 650MB for the full image, vs 50MB for the Alpine Linux version. However, there’s a note at the bottom of the...

JavaScript is rapidly evolving. With the TC39 Working Group setting the course for the language, and the larger community being involved in the process, it’s moving faster than any other language with 20+ years of history behind it. And it can be overwhelming at times – trying to keep up, trying to use new features and wondering if they are available. ...

It’s tempting to use the “:latest” tag of an image when you first get started with Docker and pulling images from DockerHub. After all, who wouldn’t want the latest and greatest version of MongoDB, Node.js, Redis, etc, when they start a project? But this is a guaranteed way to ruin your life, destroy your productivity and rip your fancy new hair style...