/explore
|
You are here 
|
chelseatroy.com | ||
| | | | |
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... | |
| | | | |
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. | |
| | | | |
blog.ploeh.dk
|
|
| | | | | How do you add tests to a proof-of-concept? Should you? | |
| | | | |
www.pathsensitive.com
|
|
| | | I'm trying to read all the good writing about software design. This is very easy because not very much has been written: it turns out that i... | ||
