4 ms·
Criticism is not bad, but is "harsh" the "only way"? Is there no utility in constructive criticism that isn't harsh? Is there really no other way to improve?
by steven777400 12y ago
Criticism is not bad, but is "harsh" the "only way"? Is there no utility in constructive criticism that isn't harsh? Is there really no other way to improve? For example, if I review someone's code who is better than me, and I learn new techniques from that review, then I have improved, even though there was no criticism involved.
Also, be careful with "always". Pedantically, all it would take is one woman coder somewhere in the world who doesn't try to be held to a different standard to invalidate your premise. I've found that the women coders I work with do not appear to expect or behave any differently in terms of standards or quality compared to the men.
- RogerL 12y agoUntil recently I've always worked in life-critical systems (bugs == death). Harshness was never required. Unceasing scrutiny was. As you say, criticism/analysis and harshness are different things. Probably some of the best leadership I ever witnessed was the lead engineer of a project walking around to each person and seriously asking "and what are you doing today to excel". You were expected to have an answer. It's never enough to just do your job, but it is enough to recognize your current limits, sometimes fail, and have a plan to improve. I try to apply that attitude every day, now over 20 years later (I'm guessing posting on HN does not go under that column, so back to work for me!!!)