When I started my first internship, I had a boss that insisted that The Mythical Man Month was one of the most important pieces of software literature ever written. I took his advice and ordered the book.
I eventually read a few chapters, got disinterested in the book, and eventually gave it away to Goodwill. What I struggled with - at the time - was the disconnect between what the book was talking about and the place I was interning at. The Mythical Man Month was born out of time spent at IBM. I was just a small local software company that used Microsoft tooling.
When my internship company got stuck on a problem, they didn't hire more people. They dialed up some consultants - who were really good at Visual Basic - to come out and help audit their code. I didn't have the context and understanding yet to know how the ideas in the book translated differently across company sizes.
Years later, I found myself at some much larger software companies. Even at the mid-size, The Mythical Man Month started to make more sense. Just as it was really settling with me, it felt like the software world completely changed.
Things have rapidly moved away from an emphasis of knowledge and specialization into a more generalist approach. Engineering concepts began to take more precedence over deep knowledge of a language or framework. While we have a really solid idea of what this shift looks like, we're not sure what "good" looks like within it yet.
Every time I see this question asked, a different answer usually comes up. This variance is both good and bad.
Good in the sense that there are definitely numerous ways to be a good Software Engineer that utilizes AI practices. Definitions of good are often very culturally local, as a result. Sometimes it can even be on a team-by-team basis. Getting to define the rules can be fun!
There's a lot of think-pieces out there around how they’ve figured out how to ship with AI. Many of them can feel bespoke to the way that a company or product is run.
Claude Code is a really good example of this. They're a frontier model provider and they have certain advantages and constraints with their products. When you read this, maybe there are things that you can take away, but it largely reads as a really cool story for what could become one day.
Then I look at Stripe's minions product. I start to see something that's a bit more shaped to places I've worked at.
These pieces are almost like stages of abstraction that allow us to break down a concept or see if more clearly - depending on what direction you're looking at.
This brings us to the bad. Variance - at a certain range - can be incredibly hard to manage outcomes for.
While I believe that the playbooks for developing software with agents is pretty well established, the management part of things is very much still in development.
Software Management is ultimately interested in shipping products and keeping margins consistent - among a thousand other smaller things. These things tend to have more human and invisible elements to them.
That's what brings us back to the Mythical Man Month. Its more concerned with the human factors behind shipping software - rather than the programatic ones.
Software Engineering has radically changed in the past two years. The way that we estimate and ensure outcomes has undoubtedly shifted as well. I don't know if we've figured out consistent ways to handle this sort of ambiguity yet.
I've been wondering if the Mythical Man Month should be re-written as the Mythical Machine Month for the modern age. It would ask the question: "How do we ship software, create systems, and ensure outcomes with Agents in the mix?"
Updated on November 20, 2026