Explore >> Select a destination
|
You are here 
|
randomwits.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. | |
| | | | |
henrikwarne.com
|
|
| | | | | I really liked A Philosophy of Software Design by John Ousterhout. It is compact and short, only 170 pages, so it is a quick read, but it contains many good ideas. The focus is on how to structure systems to make them easy to understand and work with. The author is a professor of Computer... | |
| | | | |
nakabonne.dev
|
|
| | | | | This article summarizes the concept of deep module described in the book A Philosophy of Software Design written by Professor John | |
| | | | |
www.techinterviewhandbook.org
|
|
| | | Study guides for coding interviews with focus on data structures and algorithms, including practice questions, techniques, time complexity and recommended resources | ||
