/explore
|
You are here 
|
abdulapopoola.com | ||
| | | | |
danlebrero.com
Book notes on "The Ascetic Programmer: How asceticism benefits programming, science, and the arts" by Antonio Piccolboni |
|
| | | | | ||
| | | | |
mycolaos.com
What are the Secrets of Software Design? Magic Trick: Red Flags Minimize Complexity: Deep Classes and Information Hiding Define errors out of existence Mindset: Tactical vs. Strategic programming How much to invest? New ideas discovered Key Lessons and Conclusion |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
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... |
|
| | | |||
