I am generally highly sympathetic to this sort of article because open source can be so thankless, a ton of work, and people can be jerks. He makes some excelle

I am generally highly sympathetic to this sort of article because open source can be so thankless, a ton of work, and people can be jerks. He makes some excellent points. A couple of times though I got the impression that he has some responsibility for some of the hurt he experiences. At one point he says it is hurtful when someone writes an article pointing out the “dumb” parts of python. While the word “dumb” may be less than ideal, there are by his own count 90 other committers besides him and 7 million total python contributors. Maybe he’s taking the criticism too personally. Or here, he says pointing out something is “broken” in a bug report is hurtful to him: >Assuming your contribution makes sense, you also need to pay attention to how you communicate. It is not uncommon for someone to submit a change and point out how they are trying to "fix this broken/wrong thing". I don't think people necessarily intend to be mean, but realize that when you say something like that you are telling me I failed and you're trying to clean up my mess. The put-down of saying I did a bad job does not motivate me to want to review your change, nor does it motivate me to want to contribute further if my work is just going to be viewed as bad. In my opinion, if someone talks about your work in a non personal way, and you take it personally, that’s on you. In any field we need to be able to criticize work in a way that is hopefully kind but also honest. I think complaining about the word “broken” in a bug report is over the top and potentially creates unrealistic expectations that lead to a paralyzing inability to communicate clearly.