Good ideas, but horribly dated. Object oriented programming was a mistake.

Severe issue with the book is that while a lot of the advice *sounds* good, and *sounds* like it should be true... There's really no scientific method to it. It's mainly, "here's what I anecdotally have seen and have derived", repackaged in an extremely charismatic and persuasive way. And I mean, the author's a consultant, and their entire *job* is sounding good, which tracks.

Reading this (along with other tech news) prompted me to write a whole blog-post: https://wirenook.net/blog/prove-it/