A Philosophy of Software Design
John Ousterhout
42 people recommended it in 17 threads, 2018–2025.
2 commenters pushed back on it — worth reading the threads.
What people on Hacker News said
Of recent years (and not including OO stuff in general), Ousterhout's "A Philosophy of Software Design" packs a lot in a few pages.
To be a great collaborative programmer (in a work enviornment) -> Pragmattic Programmer, Code Complete, Mythical Man Month, A Philsophy of Software Design by Ousterhout.
Probably most famous for the concept of "deep modules" (the interface should be a lot simpler than the implementation), which I like.
A book that definitely wasn't in the category I described above (for me) was John Ousterhout's Philosophy of Software Design - https://www.amazon.com/Philosophy-Software-Design-John-Ousterhout-ebook/dp/B07N1XLQ7D .
My favorite take away from A Philosophy of Software Design was to try to make low-level functions more general and high-level functions application specific/concrete.
A Philosophy of Software Design is short, and opinionated as such books go. I liked it - it articulates a few concepts that we encounter in our daily work and don’t really learn about in school.
But one tidbit I did like from the book was along the lines of "if every use case involves the same action, it would be simpler to incorporate that action".
This book brilliantly illuminates the deepest issues at the core of software development. It is a well-written, gentle read. I have been programming for close to 50 years now, and this is probably the best and most insightful book I have ever read on software development.
This one though, is a hearty dive into the delectable details of design.
John Osterhout's Philosophy of Software Design - vastly overdue, I love this book. I already apply many points presented in this book but several fragments gave me an enlightening perspective on my daily tasks
And on Amazon
Every Programmer Must Read Book
One of the best books about Software Engineering that I've read so far. The book is very clear and concise. It's written so well with easy-to-understand examples, I'm in my early career but can easily capture the author's ideas. This book mainly discusses about the "Complexity". Not the time nor the space complexity in algorithm but the complexity of human understanding the codebase. This book guides me how to produce good code and identify the bad code . If you're a software engineer who loves writting beautiful code, this book will be worth every second. Additionally, I love the list summary at the end of the book. …
Derek · verified purchase · 5/5
Beautifully-written, but with blind spots
Since 2016, my job has been to teach software design at the advanced level to professional engineers. I run workshops, speak at tech companies, and blog on software design. So when I heard of this book, I naturally took a look to see if I could recommend it to students. PoSD is best read as a tactical guide of how-to’s. About a quarter of it is spent on naming and comments, and much of the rest is about specific patterns. His few attempts to jump from tactical advice to principles are either done by trying to blur together similar-sounding tips, or are hamstrung by his inability to see the meaning of a program beyond the code. …
James Koppel · verified purchase · 4/5
Just read it. It's short. It's great.
I think every person who has written a fair amount of code should read this book. Managers should buy it for their teams. It should be required reading for new team members (it doesn't long to get through - a few hours). It is NOT for beginner programmers in my mind - you will not have written enough code to understand the points being made. I'd say it's perfect for mid-level to advanced programmers. Why for advanced? Because they can quickly get throught it, and challenge some of their own design assumptions and practices. Mid-level programmers will find it a treasure. …
Mr. Bikes, Books, Music, Watches, Tech, Stocks · verified purchase · 5/5
Where it comes up
- Ask HN: Best books on managing software complexity? 2022 · 9 recommendations
- Ask HN: Top 10 Timeless Software Books That ChangedLife as Software Engineer? 2023 · 5 recommendations
- Books for Software Engineers in 2023 2023 · 5 recommendations
- Ask HN: Best books under 200 pages for developers? 2020 · 5 recommendations
- Books that changed my career as a software engineer 2021 · 4 recommendations
- Ask HN: Suggestions for books about API design? 2020 · 2 recommendations
- Ask HN: Favorite nonfiction books of 2018? 2018 · 2 recommendations
- Ask HN: What's the best book you've read regarding software development? 2025 · 1 recommendation
- Ask HN: Books you read in 2023 and recommend for 2024? 2023 · 1 recommendation
- Ask HN: Do you recall any book or course that made a topic finally click? 2022 · 1 recommendation
- Ask HN: What are some of the best books you have read in 2022? 2022 · 1 recommendation
- Ask HN: Best book to learn C in 2022? 2022 · 1 recommendation
- Ask HN: What are the best short tech/engineering books you have read? 2022 · 1 recommendation
- Ask HN: What is the best book you read in 2020? 2020 · 1 recommendation
- Books I recommend to my software engineering students 2020 · 1 recommendation
- Ask HN: What are the most fundamental books on computer science? 2019 · 1 recommendation
- Ask HN: Books you read in 2018? 2018 · 1 recommendation
