There’s a moment in every developer’s career where the tools that made you good stop being enough.
You’re shipping solid code. You understand the systems you’re working in. But you start to sense that the most important work isn’t happening at the keyboard anymore. It’s happening in the conversations, the decisions, the tradeoffs, and the structures that nobody wrote down. It’s happening at a level above the code.
That moment is the beginning of the architect’s journey. And it’s the hardest move most engineers will ever try to make.
This newsletter is about that move.
What this is
The Software Conductor is built around the central idea of my book of the same name: the difference between a software developer and a software architect isn’t seniority or experience. It’s a fundamentally different way of thinking about your work.
A violinist in an orchestra plays their part. A conductor leads the whole ensemble without playing a single note. Both roles require deep expertise. But only one of them is responsible for the music.
The same distinction exists in software. A developer writes code. An architect creates the conditions for great software to exist. As AI gets better at handling the execution layer of software development, that distinction is becoming more important, not less.
I write about what it takes to make that transition. The technical skills, yes, but more importantly the mindset, the judgment, and the leadership that the architect role actually requires.
What you’ll find here
Pieces on architecture thinking, system design, and the practical frameworks that help engineers work above the code level. Ideas drawn from the book, ideas that didn’t fit in the book, and ideas I’m still working through. Honest takes on how AI is reshaping the work and what that means for engineers who want to grow.
I don’t publish on a rigid schedule. I publish when I have something worth saying. That usually means a few times a month.
Who I am
I’m Lee Atchison. I’ve spent my career building large-scale software systems and helping engineering teams navigate the complexity that comes with growth. I’m the author of The Software Conductor and Architecting for Scale (O’Reilly), and I currently serve as CTO at Product Genius. I’m based in Seattle.
I’ve been thinking about the developer-to-architect transition for most of my career, and writing this book gave me the chance to finally say what I actually think about it.
If you’re a senior developer wondering whether architecture is the right next step, or an engineer who’s already made the move and is figuring out how to do it well, this newsletter is for you.
Glad you’re here.
Stay up-to-date
Never miss an update—every new post is sent directly to your email inbox. For a spam-free, ad-free reading experience, plus audio and community features, get the Substack app.
To learn more about the tech platform that powers this publication, visit Substack.com.
