On reflection, I have kind of an interesting relationship with this thesis. Whether you should be quick to criticize kind of depends on the purpose of the discussion. Maybe in the context of the person writing the code that kills webservers, it was a reasonable idea. It could well be true at the same time that the software creating that context is, in fact, garbage.

I tend to think from the perspective of how to build systems tomorrow that are not garbage, so I lean towards labeling as garbage things that cause annoying code to have to be written; it's an optimistic perspective in a certain sense, that things can be better. But if you're going to bother judging past projects, which is already something to be careful with, it seems pretty clear as OP states that you'll learn more about by looking for reasons that the way they did things made sense at the time. With all the pesky humans involved, it may well be a sociological lesson rather than a technical one.