I remember the days when SysAdmins bragged about server uptimes that were sometimes measured in years. I have been out of the SysAdmin world for quite a while, focusing on software development, and somewhere along the way, a small revolution happened. Here at Threat Stack, our DevOps team embraces immutable infrastructure, which allows us to spin down problematic servers and spin up brand new clean instances in a matter of minutes. Impressed with this approach, I started to look for a way to bring some of these concepts home. Read more “DevOpsing at Home”
After moving our build infrastructure to webpack, one of the hurdles we had to overcome was finding a good way to run unit tests. Quite a few tutorials and how-tos are available for using mocha with webpack, but none of them gave us all the things we wanted from our test setup.
Therefore, as described below, we defined our requirements for the testing infrastructure and created a setup that enables us to build a test bundle from any number of spec files in a directory, incrementally rebuild on each spec change, and rerun the test suite via mocha on every change. Read more “Unit Testing With Webpack & Mocha”
There are many tutorials, blog posts, and articles in the internets that deal with using cool and shiny new tools in cool and shiny new projects. As any developer knows, useful codebases that are anything more than “Hello World” don’t stay in that hipster-happy state for too long. Even in the most disciplined teams, the tech debt grows and consumes the code; once active and well-maintained libraries gradually become forgotten and slowly await death in dusty corners of GitHub. Unfortunately, adding shiny new tools to older projects is not always well covered.