/explore
|
You are here 
|
randomwits.com | ||
| | | | |
nakabonne.dev
|
|
| | | | | This article summarizes the concept of deep module described in the book A Philosophy of Software Design written by Professor John | |
| | | | |
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. | |
| | | | |
embeddeduse.com
|
|
| | | | | "Complexity is anything related to the structure of a software system that makes it hard to understand and modify the system." John Ousterhout, The Philosophy of Software Design, ... | |
| | | | |
www.ethanrosenthal.com
|
|
| | | I make Python packages for everything. Big projects obviously get a package, but so does every tiny analysis. Spinning up a quick jupyter notebook to check something out? Build a package first. Oh yeah, and every package gets its own virtual environment. Let's back up a little bit so that I can tell you why I do this. After that, I'll show you how I do this. Notably, my workflow is set up to make it simple to stay consistent. | ||
