/explore
|
You are here 
|
denvaar.dev | ||
| | | | |
chelseatroy.com
|
|
| | | | | I recently read John Ousterhout's book, Philosophy of Software Design. This blog post includes my commentary on some parts that stuck with me. This is neither a review nor a summary of the book.1 Instead, if you and I were in a book club and this book were the topic of our next meeting, I... | |
| | | | |
third-bit.com
|
|
| | | | | ||
| | | | |
jonathan-frere.com
|
|
| | | | | This review is largely in response to the article "It's probably time to stop recommending Clean Code", and the ensuing Reddit discussion. A lot of really interesting points were brought up, but the big question that the author themself wasn't able to answer was: "What should we recommend instead?" I believe the book we should be recommending is A Philosophy of Software Design by John Ousterhout. In this post I want to spend a bit of time reviewing it and giving an overview of the contents, and then I want to explain why, in my opinion, it is such a good recommendation. | |
| | | | |
mattspitz.me
|
|
| | | software engineering musings | ||
