I think what the author is railing against is the tendency to criticize something before becoming deeply familiar with the problem

There's a tendency I've observed nearly everywhere I've worked where a developer wants to totally rewrite some piece of software because "it is garbage." In actuality, his motivations tend to be a combination of "other peoples' code is hard to read and this is not how I would have done it" and not having the depth of familiarity with a problem that you attain doing implementation work.

In any cases, asking why something is a particular way is a good thing to do.