Blog Posts

As a counterpoint to both “The Good” (where IaC worked well to support our journey), and “The Bad” (where it couldn’t solve all our problems), this is the “Ugly” side of IaC – the messes, the pitfalls, and the downright unhelpful aspects of the technology.

In my last post (read it here: [link]) I extolled the virtues of Infrastructure as Code (IaC) and described how we rebuilt a new company – Spine Energy Technology – from scratch using an existing IaC template. This extreme application of “lift and shift” proves the incalculable value of well-maintained IaC, and should give some hope to those dreamers whose disaster recovery plan is essentially just terraform apply. However, cloud infrastructure management is a complicated bea

Infrastructure as Code (IaC) is one of the more subtle, yet powerful tools in a Platform Engineer’s belt. More than just a way to codify and store the definition of (cloud) computing resources, IaC is a quintessential reflection of DevOps philosophy: the ability to apply good software engineering practices to the management of (virtual) hardware. Good IaC allows infrastructure to be reliably and repeatable iterated, tested, and released to production just like any functional