The overall goal is to reduce complexity and conversely increase the ease in understanding and maintaining the software. The book is well structured and the discussions are all well made and drice home the point of the author. It is however mostly directed at newer software developers. Interfaces, naming, descriptions, all these things are important but are just the foundation to any developer out there.

I really enjoyed reading this book, especially if you've read [b:Clean Code: A Handbook of Agile Software Craftsmanship|3735293|Clean Code A Handbook of Agile Software Craftsmanship|Robert C. Martin|https://i.gr-assets.com/images/S/compressed.photo.goodreads.com/books/1436202607l/3735293._SX50_.jpg|3779106] before. This one isn't that religious, but certainly similar opinionated. In general most of the ideas felt more reasonable, like the points about shallow and deep modules or when to split classes. Also I really like how essential code docs are for the author, because I feel the same. Normally, business code rarely includes comments at all and I usually have to make my own, to avoid re-learning blocks I've already visited.