10 books like Software Engineering at Google

Many of the most significant principles of effective software development are timeless. They’re independent of the development life cycle or model, programming language, application type, and so forth. Although this book is quite a few years old now, nearly all of its contents are still valid. The 201 principles cover the full spectrum of software engineering: general principles, requirements engineering, design, coding, testing, management, product assurance, and evolution. The descriptions of each principle are concise, whereas my 60 lessons in Software Development Pearls go into a great deal more detail and offer many practical techniques.

There’s an unfortunate tendency among young software people to disregard knowledge from the past as irrelevant to them. That’s not correct. This book can help close significant gaps in any practicing software developer’s knowledge.

Robert Glass is one of the foundational leaders of the discipline of software engineering. He’s done it all and seen it all. This book includes 55 facts and 10 fallacies about many aspects of software engineering, grouped into the major categories of management, the life cycle, and quality. Based on my own experience, I can vouch for the validity of all the points Glass makes.

These timeless truths can help you avoid going down an ineffective path, wasting time only to rediscover the same facts on your own. There’s no need to retrace the missteps from the past. Books like this can keep your energies focused where they will provide the most value to your customers.

Most books about lessons learned and good practices tell you what you ought to be doing. AntiPatterns warns you about things you should not be doing. It points out a wide range of software project approaches that the authors believe are not advisable. The antipatterns have whimsical titles such as Poltergeists, Golden Hammer, Spaghetti Code, Stovepipe System, and Design by Committee. Each pattern describes the symptoms, causes, and consequences of that particular behavior, as well as offering a restructured approach that’s likely to yield better results. As with other lessons-learned books, this book lets you learn from the pain suffered by others to avoid stepping into the same traps on your own projects.

One way to craft lessons learned is in the form of recommended best practices (or, as I prefer, “good practices”). Best practices represent collected and distilled wisdom from many observers, many projects, and many years of experience. Rapid Development includes 27 best practices for software development, with one chapter devoted to each. Although the book was published more than 25 years ago, most of these are still relevant. Indeed, several of them have been incorporated into routine contemporary practices: evolutionary delivery, designing for change, timebox development, and requirements scrubbing. Techniques such as inspections, miniature milestones, principled negotiation, and reuse are perennially pertinent.

I love pattern languages. And Team Topologies brings patterns for team types and their interactions. Most importantly, they address fundamental problems of the software industry: how teams organise for fast flow, and how teams cope with cognitive load. The book steams from the author's experience in the DevOps community, and it is widely used across the world. Last but not least, Team Topologies give us a language that support organisation evolution.

I spent my career leading software engineering at two of America’s top banks. It’s not all innovative work, as you might guess, and here is where Toyota comes in. 

Toyota teaches the difference between routine, standardized work (where we use predictive process control) and creative work (where we use adaptive process control). Balancing this in practice is a key to being a great software engineering leader. For those manufacturing-like processes (incremental feature addition, defect repair) the Toyota manufacturing way became the basis of the Agile movement a decade later: flow, pull, level work, quality the first time, process standardization and continuous improvement, and closeness to customers. Toyota Way provides a deeper understanding than any agile seminar. 

Much has changed since this book was published in 1975.

We’ve gone from phones chained to walls to smartphones you can lose behind the sofa cushions. The word “apple” went from being something you eat to something you talk into and stream movies on.

We went from ARPANET connecting a few university computers to the thoughtful, incisive forum of civil public discourse that is the internet today. (Obviously I’m kidding.)

In all of those years, however, some things haven’t changed. Management is still management, people on a development team still need to communicate, and as Brooks's Law states, “Adding manpower to a late software project makes it later.”

This book reminds us that some concepts are eternal and ideas such as the second system effect and the throwaway version are still true. (It’s also a quick and easy read that will give you something to discuss at developer cocktail parties.)

This highly informative book offers a well-written overview of most of the pandemics occurring from the “Spanish flu” of 1918 until Covid-19 of 2020. By giving a detailed historical account of everything from AIDS to SARS and Zika this book reassured me by showing how pandemics in the past had been overcome and so by implication how the Covid-19 pandemic could also be overcome. The author conducts detailed research into the exact chronology of each pandemic so that by helping to understand its epidemiology, he also creates an interesting and exciting detective story. 

It’s fascinating when terms and ideas become popular and pervasive, yet everyone has a slightly different take on what it is they are talking about. 

Coaching might be the best example ever in business. It’s a vital skill set, yet only in the last couple of decades have we begun to effectively grapple with what it is, how to do it, and the outcomes it produces.  Sara Canaday’s book is wonderful because it addresses these issues with great focus and clarity.

It’s the perfect first book for anyone who wants to dive in to coaching. It’s not too complex or academic, rather quick and applied. She offers a model, helps you understand how to actually use it, and sets you up to engage coaching far more effectively.