The Type-Safe Builder pattern is well understood when used within the confines of a single project. But what happens when you expose it as part of the public API of your module - how do you handle that API's evolution over time? This article covers that topic in great depth.
I've recently changed the tech stack powering this blog, abandoning Ruby on Rails in favor of NodeJS and the Metalsmith library. In this article, I talk about the details of the migration - the justification behind it, why did I choose that stack that I did, and how did the migration itself go.
Version 1.4 brings with it support for TestNG as the execution engine.