Software Engineering at Google versus Tidy First?.
Both show up on every "best" list. They're not competitors. They're a sequence. Here's which one to read first, and when.
Reviewed by Ashish Sheth · Updated June 2026
Option A
Software Engineering at Google
Titus Winters, Tom Manshreck, Hyrum Wright · 2020
READ FULL REVIEW →
Author
Titus Winters, Tom Manshreck, Hyrum Wright
Kent Beck
Pages
599
122
Published
2020
2023
Publisher
O'Reilly Media
O'Reilly Media
Level
intermediate to advanced
intermediate
Amazon Rating
4.6/5 (712)
4.4/5 (420)
Goodreads Rating
4.32/5 (1,480)
3.92/5 (1,115)
Software Engineering at Google
Strengths
+ Honest about what worked, what didn't, and what's specific to Google's scale
+ Best available treatment of large-scale code change and deprecation
+ Each chapter stands alone — you can read just the topics you need
+ Coined Hyrum's Law in a form every engineer should internalize
Caveats
− Some chapters are heavy on Google-specific tools (Blaze, Critique, Piper)
− Cultural chapters can feel like recruiting marketing in places
− Less directly applicable at a 10-person startup than at a 1,000-person company
Tidy First?
Strengths
+ Tiny book, finishable in an afternoon
+ Every tidying maps directly to a habit you can use this week
+ Kent Beck's voice is unmistakable: opinionated, experienced, generous
+ Splits the design discussion from the daily tactics so each lands cleanly
Caveats
− Several readers feel the theory section (Part III) is rushed and abstract
− Examples are tiny and toy; some want bigger refactoring case studies
− Costs about the same as much longer books, which annoys some readers
The verdict
Read Tidy First? first to build foundations, then move to Software Engineering at Google for advanced concepts.
Software Engineering at Google
Check Price on Amazon →
Tidy First?
Check Price on Amazon →
Frequently asked
Which is better, Software Engineering at Google or Tidy First??
Read Tidy First? first to build foundations, then move to Software Engineering at Google for advanced concepts.
Is Software Engineering at Google only useful if you work at a big company?
Most chapters apply at any team size of about 20+ engineers. The book is explicit about which practices need scale to pay off and which work even on small teams — read the testing, code review, and deprecation chapters first; treat the monorepo and infrastructure chapters as context.
Is Tidy First a replacement for Fowler's Refactoring book?
No. Refactoring is the comprehensive catalog; Tidy First is the everyday discipline. Read Refactoring as a reference and Tidy First as the habits guide. They complement each other rather than overlap.