I Wrote a Book: Software Product Development Without Stupidity
My book is out. It’s called Software Product Development Without Stupidity: How Not to Sabotage Your Odds in an Already Hard Game. It’s on Amazon in paperback, hardcover, and Kindle (UK, US), and on Leanpub as a DRM-free PDF and EPUB.
If you’ve been reading this blog, you’ve seen pieces of it already. I tried to write a book several times, and every time it ended up as a handful of blog posts. Some of them grew into chapters:
- The product manager role is a mistake
- At the heart of the burnout epidemic
- Lifers and politicians
- So you think you work in a team
- Start with a skeleton not to die a zombie
- Introducing Abstraction Deviation Impedance
In the book they’re rewritten and tied into one argument.
Why I wrote it
Over the years I’ve talked about software product development with many people, in many places, and most of them were frustrated. They knew how to fix their company’s worst problems and weren’t allowed to. These were competent, senior people who cared about their customers and their craft. All they wanted was to do their best work, and somehow they couldn’t.
Whether it was over a pint or in a meeting room, it was always the same story. Those conversations are where this book comes from.
What finally unblocked me was Luca Debiasi, a former colleague and a friend, who at some point stopped letting me off the hook. Put it together, he said. By then, the pain of writing a book had become more tolerable than the pain of leaving heartfelt things unsaid.
What it’s about
Most software companies are full of smart, dedicated people. So why do the products keep getting worse, the costs keep climbing, and the people work harder than ever?
My answer is the system they work in. Competent, well-intentioned people make choices that end up harming the company, the product, and themselves, because they misunderstand the system they’re standing in. That’s what I mean by stupidity.
The book follows it from the top down: what a company is for, how people are hired, paid, and organized, how a company keeps its capability to change, and then the architecture, the code, and the practices that decide whether a product can keep changing. There’s also an interlude on AI, and on why speeding up a broken system only gets you its bad results sooner.
It’s written for founders and leaders, and it stays technical enough to be worth a developer’s time.
What it isn’t
It isn’t a manual. No seven steps to success, no frameworks, and no case studies either. I take strong positions, and some of them will irritate you. Good. A polite book full of niceties and platitudes would waste your time and mine.
I’m also not trying to convince you of anything. People don’t change their minds because someone argues harder. They change when they meet a way of working that obviously works and get curious, or when they run into a contradiction their current beliefs can’t explain. So the book shows you how I’ve come to see things, and leaves the rest to you.
If you read it, let me know what you think.