A more humble book, with a more grounded approach might be: _A Philosophy of Software Design_ by John Ousterhout (the guy behind Tcl) https://www.goodreads.co

A more humble book, with a more grounded approach might be: _A Philosophy of Software Design_ by John Ousterhout (the guy behind Tcl) https://www.goodreads.com/book/show/39996759-a-philosophy-of-software-design https://www.goodreads.com/book/show/39996759-a-philosophy-of... Written as the textbook for a software engineering course, it developed out of that course being taught multiple times _and_ all the code reviews which that entailed. Previous discussions/mentions here which had a notable number of comments: https://news.ycombinator.com/item?id=41017367 https://news.ycombinator.com/item?id=41017367 https://news.ycombinator.com/item?id=34733120 https://news.ycombinator.com/item?id=34733120 https://news.ycombinator.com/item?id=17779953 https://news.ycombinator.com/item?id=17779953 https://news.ycombinator.com/item?id=8055868 https://news.ycombinator.com/item?id=8055868 I re-wrote my current project in the course of reading it (I would read a chapter, then read through the code and where appropriate apply the relevant principle) and once I finish the current re-write (from OpenSCAD to Python) will be repeating that process to see if what I was supposed to have learned stuck/survived the re-write.