Why read Software Engineering at Google?

Book cover of Software Engineering at Google: Lessons Learned from Programming Over Time

Book description

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering.

How can software engineers manage a living codebase that evolves and responds to…

Explore

Topics

Genres

Coming soon!

When you buy books, we may earn a commission that helps keep our lights on (or join the rebellion as a member).

Why read it?

2 authors picked Software Engineering at Google as one of their favorite books. Why do they recommend it?

Chris Zimmerman

Author

A thoroughly fascinating (and fascinatingly thorough) look at engineering practices at Google.

It’s an encyclopedia written by a bunch of authors, so some of the chapters are a little dry, but for those of us who aren’t on teams with 25,000 engineers it’s spell-binding to see what programming at that sort of scale looks like. Some of the chapters prompted us to think really hard about the way we do things at Sucker Punch.

From Chris' list on programming for people who want to be good at it.

Karl Wiegers

Author

This hefty and contemporary volume provides a wealth of recommendations about how to build high-quality, large-scale software that’s intended to endure for an extended period of time. The book contains sections on culture and leadership, processes, and tools. It describes many effective practices for testing, configuration management, continuous integration and delivery, code reviews, code static analysis, and documentation. Not everyone is writing software on the scale that Google does, but the many comprehensive and specific examples in this book can be applied to nearly any software development project.

From Karl's list on lessons about software development.