As a general rule we should try better to understand why the designer has made the decisions they’ve made and think about their experience and how we can help, not just humiliate them. Take the time to provide newbies with the resources and answers that they need. That’s education.
Especially pointed given how easy it is to offer a knee-jerk reaction on the internet. Of course, I’ve never done anything like that.
The same notes could be applied to developers too. It’s easy to become dismissive of someone’s work because they did it in an unfashionable language, or a different coding style, or used some sort of kludgy hack. There was likely a reason behind the decision, which may be worth examining before picking up the pitchfork.
Updated: Upon further reflection, they should not be called design critics (we’ll go with Dan’s original intent). Also, forgot to link to actual article.