Infrastructure as Code

Last week I participated in Thoughtworks’ Future of Software Development retreat.

AI agents build software quickly, but they don’t default to building systems with great operational quality.

I spent last week in Bengaluru with the Doppler team, working on volume 34 of the Thoughtworks Technology Radar.

We’ve removed the dev/ops wall.

(Part 2 of The Infrastructure Automation Problem) In my previous article, I observed that many engineering leaders find infrastructure management to be a bottleneck for software delivery, even after adopting cloud and infrastructure automation.

Many engineering leaders I talk to are frustrated with their infrastructure automation.

In January I set up an “Infrastructure Effectiveness Survey” and asked people to fill it in, promising that I’d share what I learned from it later on.

The idea that you can go faster by sacrificing quality, or improve quality by moving more slowly, is a false dichotomy.

Most Infrastructure as Code management tools today are designed for workflows where infrastructure engineers write low-level infrastructure code, and are also responsible for deploying that code to create and update environments.

One of the early promises of Infrastructure as Code was to do away with snowflake servers.