Developer Hegemony
It's been said that software is eating the planet. The modern economy-the world itself-relies on technology. Demand for the people who can produce it far outweighs the supply. So why do developers occupy largely subordinate roles in the corporate structure? Developer Hegemony explores the past, present, and future of the corporation and what it means for developers. While it outlines problems with the modern corporate structure, it's ultimately a play-by-play of how to leave the corporate carnival and control your own destiny. And it's an emboldening, specific vision of what software development looks like in the world of developer hegemony-one where developers band together into partner firms of "efficiencers," finally able to command the pay, respect, and freedom that's earned by solving problems no one else can. Developers, if you grow tired of being treated like geeks who can only be trusted to take orders and churn out code, consider this your call to arms. Bring about the autonomous future that's rightfully yours. It's time for developer hegemony.
Stats for nerds
26recommend
55mentions
43people
2016–2026years
58% recommend38% neutral4% critical
Mentions per year
What Hacker News says
- It’s especially ironic since the bean counters produce no value. I like ‘Developer Hegemony’, even if the title needs changing. The author makes a great case for why information workers produce almost all the value. It’s them that make the profits, yet they’re always a cost center.
- Developer Hegemony [1] will help your thinking on how to price software in a world that traditionally rewards business people, as well as being pretty emotionally revealing about the trade we’re involved in.
[1] - https://books.google.com/books/about/Developer_Hegemony.html...
- Cue ‘Developer Hegemony’, a great book on this topic. Yes, as an engineer, you should be interested in vision/strategy/product. Otherwise you’re just executing, and the opportunists will get promoted ahead of you. The book explains it much better than me.
- I recommend "Developer Hegemony". Coming from a career in FAANG, it's helped put words to what bothers me about the power dynamics and management practices. The book also presents a picture of what a healthier and more empowered "software engineering" role/world could look like (one of my 2023 goals is making significant career moves in that direction)
- Really great to see a mention of "Developer Hegemony" here.
The author compares software engineers to doctors or lawyers.
In a law firm, the partners call the shots and the rest of the staff is there to support them. In tech companies, the structure is inverted. The engineers are at the bottom of the power hierarchy, even though it's the engineers that generate the most value.
The author suggests that developers should instead become "efficienciers". Rather than being code monkeys, "efficienciers" are able to solve problems via their use of technology.
@losteric I've been thinking about this book for a while. If you're willing to share what your plans are, I'd love to hear more. To me it sounds like some sort of freelancing which is rather daunting.
- This rings a bell for me too... have you read Developer Hegemony? It reminds me of that book.
Related
Domain-Driven Design Distilled
6 recommend · 11
Domain-Driven Design
104 recommend · 252
The DevOps handbook
22 recommend · 52
Waltzing With Bears
9 recommend · 17
The Pragmatic Programmer
353 recommend · 700
Debugging the development process
6 recommend · 9
2018–2026
Refactoring UI
129 recommend · 167
