Hacker News new | ask | show | jobs
by basicallybones 1127 days ago
You should try to develop an accurate and nuanced view on your skillset. I am simultaneously quite proud of my guitar playing and acutely aware of my deficits. For me, when someone points out a problem I did not realize/perceive, I am thankful (if it comes from the right place). Building your own skill, confidence, and humility (as you try and fail) is the best way to develop resilience against criticism.

You also should develop a supportive peer group. I cannot emphasize how important this is. You probably will not find it at your job. Find friends you admire, and try to be the kind of person they admire.

Constructive criticism should always flow freely both ways. In most professional environments, this does not happen. (Criticism flows down the Org chart.) This is an inherently toxic situation.

Keep in mind, insults can masquerade as criticism. Snarky comments are insults masquerading as criticism (though they may be well intentioned).

Work environments are tough. I have had situations where a manager far less technically skilled than me criticized an architectural recommendation, the business now deals with the consequences of those decisions (bugs, instability, excessive resource usage), and I am comfortable (bemused) because events proved I was recommending the correct decision and I have a support network outside of work. This sort of situation is toxic to improvement if you are not careful. I suspect many people find themselves in these situations professionally so often they just consider it normal.

1 comments

One more thing: I have seen managers blame engineers for their own planning/resource allocation mistakes. If you are a mid-level engineer, these mistakes feel like they are your fault. But zoomed out, they are a process/planning/management problem. If you do not have enough experience, you might not even realize the difference.