Well, today we officially launch the book, Developer Hegemony. I’d like to thank everyone who followed along, offered feedback, bought books, and generally supported the efforts. I’ve enjoyed the ride and I hope you all love the book. Also, congratulations to the winners of the Thunderclap raffle: Justin Neff, Jim Wang, and Gintautas Miselis! I will be sending free copies their way. Thanks to them and to everyone that participated!
In the final days of writing Developer Hegemony and throughout launch preparation, I wrestled with an elevator pitch. As regular readers know, you wouldn’t find “brevity” listed on my resume, even if making resumes was something I did. And so I struggled. But I think I have it now.
“Why aren’t software developers in charge of the software development industry? Developer Hegemony explains why not, and it explains how we fix that problem.”
Today, I’ll explain the book by expanding on this elevator pitch a bit.
Who’s In Charge Here, Anyway?
So, if software developers don’t run the industry, who does? To answer that question, understand the context in which most developers write software. It happens in the corporate world, which consists of companies shaped like pyramids.
Reminiscent of military organizations, a tree-like chain of command serves as the scaffolding for most companies. The CEO gives orders to a handful of C-suite members. These people, in turn, give orders to a larger number of vice presidents, who then give orders to a whole bunch of directors. The directors then give orders to hordes of managers, who pass those orders down to legions of grunts. Finally, with the grunts, you arrive at the leaves of the tree and the bottom of the pyramid.
And those leafy grunts write the world’s software, carrying pyramids of management upon their backs. So who is more important than software developers in the business of software development? Literally gigantic pyramids of management. Oh, and you can also toss in some people who technically exist in the same level of the reporting organization but have titles like “analyst” or “project manager.”
So the question shifts from “who is more important than software developers in the business of software development?” to “who isn’t?”