Sounds quite a bit like the principles put forward in Ousterhout's _A Philosophy of Software Design_ https://www.goodreads.com/book/show/39996759-a-philosophy-

Sounds quite a bit like the principles put forward in Ousterhout's _A Philosophy of Software Design_ https://www.goodreads.com/book/show/39996759-a-philosophy-of-software-design https://www.goodreads.com/book/show/39996759-a-philosophy-of... https://web.stanford.edu/~ouster/cgi-bin/book.php https://web.stanford.edu/~ouster/cgi-bin/book.php which has seen a fair bit of discussion here: https://news.ycombinator.com/item?id=17779953 https://news.ycombinator.com/item?id=17779953 https://news.ycombinator.com/item?id=31248641 https://news.ycombinator.com/item?id=31248641 https://news.ycombinator.com/item?id=37975558 https://news.ycombinator.com/item?id=37975558 https://news.ycombinator.com/item?id=17906662 https://news.ycombinator.com/item?id=17906662 and there's a video: https://www.youtube.com/watch?v=bmSAYlu0NcY https://www.youtube.com/watch?v=bmSAYlu0NcY (which has also been discussed) I read it when I got stuck on a recent project, and paused after each chapter to review _all_ of the code (fortunately, it's a fairly small project) and to apply the principles from that chapter to the code, and it was a big help and got me over the hurdle to a working version.