<ul><li>A Philosophy of Software Design by John Ousterhout focuses primarily on what separates good software design from bad software design.</li><li>Understand why you disagree with coding advice found in books like this one or Clean Code.</li><li>Complexity in software is more apparent to readers than writers.</li><li>Good design should be obvious; symptoms of complexity include change amplification, cognitive load, and unknown unknowns.</li><li>Modules should be deep and complex implementations hidden behind simple interfaces with sensible defaults.</li><li>Try to pick approaches that are radically different from each other when designing software.</li><li>Comments should be used to explain things that can't be expressed in code and the biggest challenge with cross-module documentation is finding a place to put it.</li><li>Enforce coding conventions and coding style preferences using automated tools like ESLint and Prettier.</li><li>Concentrate on strategic programming and don’t focus just on features.</li><li>Tests, particularly unit tests, play an important role in software design because they facilitate refactoring.</li></ul>

Lessons from A Philosophy of Software Design

Discover more