Archive

This article is Part 2 in a series exploring Aggregate Resources and rethinking Infrastructure as Code. If you haven’t read Part 1 yet — Why Infrastructure as Code Sucks — I recommend starting there for more context. It lays the groundwork for the ideas we’ll be diving into here. In

Let’s admit it: infrastructure as code sucks I have spent most of my career wrestling with it, so admitting it isn’t exactly easy or fun. But the truth is, even if it’s the best we have, it feels like infrastructure as code is stuck in time and