Goal
The path to "Googleのソフトウェアエンジニアリング"
Here is the reading path leading up to this book, derived from its dependencies and ordered from the fundamentals.
The path so far (3 books)
Why read this first: Once unit tests form a solid base, you stack integration, contract, and end-to-end tests in the right proportions along the test pyramid, scaling up to a system-wide quality strategy. The rule is many at the bottom, few at the top.
Why read this first: Once testing and CI/CD give you a foundation for building in quality, you frame how it affects organizational delivery performance through measurement. DORA's four key metrics show empirically that speed and stability are not a trade-off.
Why read this first: Once you can improve delivery performance through measurement, you widen your view to the engineering culture and practices that sustain it at scale and over time. Google frames this as 'programming integrated over time.'