Software Engineering at Google

Google's account of the practices that let thousands of engineers work in one codebase over decades, organised around culture, processes and tools. The opening argument is that software engineering is programming integrated over time, which is what makes code review, testing, deprecation and dependency management central rather than incidental. Later chapters cover the monorepo, large scale changes, static analysis, continuous integration and the build system. Much of it assumes a scale most organisations will never reach, and the reasoning about why practices break down as time and headcount grow travels well below that scale. Useful to a delivery lead who wants to argue about engineering standards from evidence.