I've been banging the testing drum for so long I'd have a hard time to not violently agree with that article. I have a couple of beefs with it though, like the sacrificing encapsulation point but other than that...

Interestingly, I'm going through this book right now and indeed I have to agree with most of this article. It didn't age well, it's become a mix of nice advises, things which are kind of obvious nowadays and points which are clearly obsolete. I find that "The Clean Coder" (different topic I know) aged way better. I think I'll give a shot to the proposed alternative book to see...

Very good advice, there's a lot in programming which is really just mundane and boring. That doesn't make it easy but you might end up doing what everyone else tried to avoid.

Or why you should think twice before embarking into a refactoring when it's not directly related to some feature development...

Good exploration of what "engineer" and "engineering" means. Also helps to overcome what software people like us assume is done by the "real engineers" while in fact sometimes they can be as sloppy than us.