August 14, 2026

I’ve been writing software for three decades. I’ve watched the work change as the machines changed — from writing everything by hand to standing on layers of libraries, services, and infrastructure built by other people. With each layer the systems became more capable, and the work became more distributed. Responsibility never distributed with it.

For the last several years I’ve been listening to people explain generative AI and coming away with the same uncomfortable conclusion: we haven’t found the right language for what’s happening. The explanation is almost always one of two things. Either it’s peak hype-cycle marketing — everything is about to be automated, every job transformed — or it’s the mirror image, a cynical account where the technology is only a confidence trick and nothing important is changing. Both are reactions. Neither is a sufficient description of the work.

I started looking for a better description by writing fiction. The Condition Set trilogy is about people trying to live with systems that are increasingly capable, increasingly difficult to inspect, and increasingly entangled with institutions that can’t simply turn them off. In one of the novels, regulated industries are required to keep a certified orchestrator on the team. The title started as world-building. But the more I wrote the word, the less it behaved like a science-fiction detail. The role kept making sense.

This book is my attempt to put that role into the present tense. It defines orchestrator as the emerging post-programmer IT job title — the person who decides what can be delegated, how a delegated system will be evaluated, what context it receives, where its authority ends, and when the whole operation has to stop. That is engineering. It changes ideation, support, production, review, and the relationship between a person and the systems they answer for.

I’m releasing this book as a free resource, chapter by chapter, because I think the conversation about how this area evolves needs to start before the job titles settle. The book is still being written. What’s available today is a draft — chapters are being revised, reordered, and added. If you’re doing work that looks like orchestration under a different title, or if your organization is struggling with where these tools belong, I’d like to hear from you.

You can read the chapters online, download the current draft, and join the mailing list to get notified as new chapters are published.

— Tim O’Brien