Chapter 6. Infrastructure: It’s Where the Power Is
Charity Majors
“Why infrastructure, why ops?” a coworker asked me, years ago. It was a software engineer, after a particularly gnarly on-call rotation, and the subtext was crystal clear: was I tricked into making this career choice—the sacrifice of being tethered to a pager, the pressure of being the debugger of last resort? Who would ever choose this life?
Without missing a beat, I answered: “Because that’s where the power is.” Then I stopped in surprise, hearing what I had said. We aren’t used to thinking of infra as a powerful role. CS (computer science) departments, the media, and the popular imagination all revolve around algorithms and data structures, the heroic writer of code and shipper of features.
To business people, operations is a cost center, an unfortunate necessity. This is a historical artifact; operations should be seen as yin to development’s yang, united and inseparable, never “someone else’s job.” Biz is the why, dev is the what, and ops is the how. Whether your company has one person or one thousand.
Code is ephemeral. Features come and go. Crafting a product in a modern development environment feels to me like erecting cloud castles in the sky: abstractions atop other abstractions, building up this rich mental world in your mind.
Software engineers are modern magicians, crafting unthinkably ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access