You have no manager, but you have no direct reports. You have influence, but no authority. Orosz interviews real Staff+ engineers from Uber, Stripe, and Google to show you how to lead without a title.
We all know the testing pyramid (Unit > Integration > E2E). Orosz acknowledges that the pyramid is idealistic. In the real world of microservices and legacy monoliths, you need a "Testing Diamond" or "Trophy." He provides specific strategies for where to invest your testing budget when you have zero time.
It is practical, cynical in the right places (he acknowledges that politics exist), and optimistic about the craft. The Software Engineer-s Guidebook
The One Book Every Senior+ Engineer Should Read: A Review of “The Software Engineer’s Guidebook”
Don’t let the title fool you. This isn't just for Junior devs. You have no manager, but you have no direct reports
You are the go-to person for every fire. You are tired. The book provides a blueprint for "Delegation and Dismissal"—how to teach others to fight fires so you can work on prevention.
I have about 50 highlights, but here are the three concepts that fundamentally changed how I view my job. We all know the testing pyramid (Unit >
Gergely Orosz’s The Software Engineer's Guidebook isn't about syntax or algorithms. It is the missing manual for the career of software engineering. Having spent the last month digesting this 600+ page beast, I believe this is the most valuable career book for engineers since Staff Engineer by Will Larson.
Have you read The Software Engineer's Guidebook ? What was your biggest takeaway? Let’s fight about the Testing Pyramid in the comments. 👇
Also, if you are looking for code snippets, there are none. This is 100% soft skills, strategy, and career mechanics.
