Actually here is an example of why a developer sometimes shouldn't lash out in public. Let's be generous and take this sample size of one and apply it to reach the reasonable conclusion that developers shouldn't, generally, lash out in public. Taking criticism personally has, at best, a tangential connection to this example. You can take every word of criticism as a personal affront to your dignity and still take it on the chin and maintain your composure, or you could disregard every word of it without pause and still react poorly out of intellectual arrogance or simply from pressure.
Most criticism isn't personal, and you shouldn't take it personally. However, some criticism is personal, and a good deal of criticism has personal implications. It would be far wiser to consider each piece of advice on its qualities, rather than make blanket assessments. When it comes to taking criticism personally it would be my advice to consider how equipped the source is to judge your personal qualities and their motivations for doing so. I do understand, however, that making such distinctions becomes more complicated when the criticism is directed toward your work, ideas, or words.