Yes, the tone is a far cry from the cool-headed, neutral, sterile aesthetic one would expect from technical or academic writing. However, the article is very informative, and should probably be bookmarked for later reference --- in case one ever has to do this kind of work.

The article may have been written in anger, and thus it provokes anger. Good! Programmers who don't get angry while solving hard, inconvenient, uncomfortable problems are, in my experience, unlikely to truly solve those problems --- sweeping issues under the rug, or passing the problem to someone else is more likely. Anger is a very powerful motivational force if honed correctly, whereas contentment often leads to docility, complacency, and quitting.

I find that problems that make you angry or enraged are simultaneously: important and instructive. Most performance problems (or even multi-threading problems), for example, fall into this category.