DaedTech

Stories about Software

Book

For the last couple of years, I’ve been working on a book called Developer Hegemony.  You’ve come here to learn a bit more about it.

What’s the Book About?

I’ve heard it said that “software is eating the planet.” And yet, for all that the modern economy and the world itself relies on software and for how sought after the skill is, software developers occupy largely subordinate roles in the corporate structure. Doesn’t that seem a little bizarre?

In this book, I explore why that’s the case. As a spoiler, I’ll tell you that I consider the standard corporate structure to be a terrible way to manage knowledge work, but the explanation goes much deeper than that.

But the book doesn’t just take you through what’s wrong. It’s ultimately a guide to how we, as software developers, can claim a better seat at the table of controlling our own destinies and establishing autonomy. I project what I think the industry is going to look like down the road and offer thoughts for how we can usher in a better future more quickly.

Who Would Be Interested?

First, and most obviously, the book would be interesting to any programmers.  There is absolutely nothing language or tech specific in it.

But beyond that obvious audience, anyone in the field of tech would also have reason to read.  In fact, anyone with a career in knowledge work professions should have some interest.  I write about developers because I know software development, but the principles herein apply to knowledge work in general.  If you have interest in office politics and better ways to work, then I’d suggest you give it a try.

What’s “Hegemony”?

People commonly ask me to define this word that I’ve put into the title. Simply put, you can associate it with dominance.  I contend that the next decade will see software developers begin to manage the software industry, instead of being managed into driving it.

Project management, marketing, accounting, sales, etc.—all matter. They matter a great deal. But in the software firms of the future, developers will not know those departments as peers; developers will run the firms and delegate those responsibilities.

When Will You Release It?

We have yet to settle on an exact launch date, but look for publication sometime in March.  I’ll update this page with more details as we know more.

I Want to Read Some of It!

You’re in luck! Sign up for my mailing list to receive a few chapters as a PDF and to get updates when the book comes out.

Want more content like this?

Sign up for my mailing list, and get about 10 posts' worth of content, excerpted from my latest book as a PDF. (Don't worry about signing up again -- the list is smart enough to keep each email only once.)