Ask HN: How do you not take criticism of your work personally?
601–610 of 653 posts
Re: Ask HN: How do you not take criticism of your work personally?
#602Earlier quoted context omitted.
Uhm...I have to chime in here. "Anti-fragile attitude" when it comes to criticism is not built by tolerance. Quite the opposite actually. It is a common misconception. While making yourself numb against criticism IS a solution but not by far the best one. A high criticism tolerance is learned by understanding that ones self worth is not attached to output or delivery. (This is hard in our industry) It comes from self…
>"Anti-fragile attitude" when it comes to criticism is not built by tolerance. Quite the opposite actually. I agree with your overall statement, but I think the specific point above could be misinterpreted in a nonconstructive way. What it seems like you're trying to say is that we shouldn't just be learning how to deal with criticism by tuning it out or building up defense mechanisms against it. That I agree with. H…
The opening was that comment A was saying something about how they did and comment B was asking probing questions. I recognized that B was leading A towards a certain framing she had in mind(a very Uncle Bob, OO patterns are the answer kind of answer), so I injected a flat "there's nowhere else that code needs to be except one of these two places, classes have nothing to do with it."
B responded with "but surely they have to be in a manager class right?" And seeing the resistance to taking any other framing, I got more assertive and instructive in my reply, giving specific recommendations to try dispensing with OO and experiment with writing more primitive code. This was the offense, and it became an argument, which was basically a stomping because I was very prepared with sources and a rationale for why I am making that recommendation, and B fell into defenses from experience and authority, talking about numbers of lines of code and systems she had made and accusing me of speculating about her ability.
And then I said, "that's nice, but I'm the comments section." Apologized for the offense, and pointed out that she started replying to A by speculating, and had admitted as much. Finished with encouraging words for B continue writing the code that she felt works best.
She wasn't happy with this, and said I "hijacked" the thread and used a "condescending tone", but also allowed that I said interesting things.
And it's like, was it worth getting into another "arguing with strangers on the Internet" cycle? Part of why I engaged in the way I did was because I was coming off a period of answering other people's questions, so it was, at first, just one more of those.
But afterwards I realized that what I had disturbed was the belief system. The original thread was an attempt to confirm B's belief to herself: that's why it was done in a leading manner. A lot of comment threads proceed along those lines. When I just wander in and negate that, defensiveness is immediate. Saying "it can only be these two things" is only condescension if you're certain that your other way is already right. B wanted to brush it off. What I was doing was starting the "put on the glasses" fight scene in They Live.
And I think part of why I've gotten better at navigating those threads and critique generally, even if I might be overbearing or "condescending" at times, is because I can recognize when a principled defense is taking place. Good technical discussions start from a place of philosophical credibility. They don't start from norms("this way is best") and then question-beg their way into justifications. They lay out the assumptions of what's true and what's being achieved, like "eliminating a form of error"(one of the goals I outlined in that thread, and the one which ultimately made B concede) and then find conclusions inductively, deductively or abductively. Once you get away from the philosophical goal and only aim for winning the argument, you start crafting harmful rhetoric.
So the answer for me lies in philosophical training: you do have to intentionally "turn it on" to think in those terms, but it lets you be more effective around criticism, to "dance" with it and see it as a process, not a prelude to violence.
And it is much harder to deal with open comments than any one specific critic, because those are subject to mob mentality. Offend a belief the mob holds in high regard, and regardless of the principles involved, you'll just get dehumanized right away. I try not to find myself involved with that stuff anymore, but it's like, yeah, of course I have beliefs.
Re: Ask HN: How do you not take criticism of your work personally?
#603Your work is not who you are. Your work is not who you are. Your work is not who you are. Really internalizing that is step one. You are smart enough. This one is a lot more subtle but worth a ton if you can internalize the implications of it. The fact is others are smarter than you, some aren't as smart as you, and the truth is you really shouldn't care. What you do need to realize is that for all of us it boils dow…
Re: Ask HN: How do you not take criticism of your work personally?
#604I don't know how healthy this is but: I haven't run into many people who are harder on my work than I am. I have an attitude that there's absolutely nothing I do that can't be improved. This may sound miserable on the surface, but for me it's actually quite freeing. It has the effect of making it easier to accept that things aren't actually going to be perfect (so it can help avoid the trap of over-engineering) and a…
I believe that both of these responses can be valuable when handled correctly, but doing so requires a different strategy for each. Actually, the first step is the same for both: make sure that you've had the correct response: if you're sad, double check the criticism really is accurate; if angry, double check the criticism really is wrong. I think perhaps a lot of trouble can be attributed not to having one of these upset responses, but to having the wrong one! A helpful side-effect of thinking about the other kind of response is that they both mediate the other: thinking about situations/new evidence in which one might respond the other way to the same criticism alleviates the original emotional response.
The next steps are more involved and specific to each response but this comment is already longer than I meant it to be :).
Re: Ask HN: How do you not take criticism of your work personally?
#605Re: Ask HN: How do you not take criticism of your work personally?
#606What you have encountered is actually one of the necessary steps to really become "a senior developer". And congratulations, you have already passed the biggest part of that hurdle: becoming aware of the issue. There are things that are fragile, things that break when they encounter a shock. Such as porcelain, when transported. There are things that are non-fragile, things that do not break when they encounter a simi…
Uhm...I have to chime in here. "Anti-fragile attitude" when it comes to criticism is not built by tolerance. Quite the opposite actually. It is a common misconception. While making yourself numb against criticism IS a solution but not by far the best one. A high criticism tolerance is learned by understanding that ones self worth is not attached to output or delivery. (This is hard in our industry) It comes from self…
Re: Ask HN: How do you not take criticism of your work personally?
#6072. They way we "judge" other people could indirectly be the way we "judge" ourselves. When you encountered somebody else making the same PR mistake what would you do or think about the person? I encountered a very similar humbling experience and I found out that I judged people very easily (although I didn't verbalize it) and it affected how I perceive the mistake I made myself. In my case, I learned to be more compassionate and passionate, and to judge people less based off their mistakes
Re: Ask HN: How do you not take criticism of your work personally?
#608To speak to the point about the PR comments, it's quite tricky to get a sense of the intention behind them. In the last few years I have adopted the approach of conventional comments, which has helped a lot with conveying that intention. I.e. if I want clarity around a code choice it's clear to the developer that I need more context, or if I have a nitpick to point out it's clear that that's why I am pointing it out.…
Re: Ask HN: How do you not take criticism of your work personally?
#609> Do not attribute to malice that which is adequately explained by incompetence. It's rare that people are trained in the art of criticism. Most of us try our best, but often fail at criticising the work while separating it from the author. It's hard to criticise while simultaneously empathising with the target. I often think of this when I've received criticism that stings. Most of the time it's simply carelessly wr…
Re: Ask HN: How do you not take criticism of your work personally?
#610Earlier quoted context omitted.
Two questions. Can a slacker goodfornothing McDonald's-working college dropout that only live day to day, party to party, feel self-worth or should they feel worthless? Can I as a senior software developer base my selfworth on the same value system as that college dropout even though I finished college? Aka if I made an honest mistake in my pr, I wouldn't have to feel bad and decrease my selfworth even though I think…
> Can a slacker goodfornothing McDonald's-working college dropout that only live day to day, party to party, feel self-worth? Do they throw good parties? Do they help their friends celebrate their successes and provide succor in times of need? If so, why shouldn't they feel some self-worth?