Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

A few potentially false assumptions. The (very real) possibility of being wrong exists, but declaring that because of it nobody ever—or you specifically—can be right seems overkill and contradictory to the ethos of the engineering profession and the approach it uses for its chosen range of problems.

(I have the vague impression that people who talk along these lines usually think that being wrong is somehow a bad thing, or at least that even if they personally don’t others do and those others need to be accomodated.

Of course, while being wrong might not be pleasant, it’s absolutely necessary, and the harder the problem is the more times you’ll need to be wrong before you solve it. Thus shaming people for being wrong, especially in an educational setting, is one of the very small number of things that make me genuinely furious. Not telling people they’re wrong when [you think] they are because you think they might feel shame because of it is... not as bad, but still feels seriously counterproductive. I can’t say I have a grip on how to train or at least help others out of that shame, though.

Is your motivation different here? Because, I don’t know, you seem to say that telling others they’re wrong [about an engineering problem] always [or often] constitutes arrogance, and that is such an extrodinarily extreme position from where I’m standing that I can’t convincingly model it.)



Drop your insistence on a dichotomy of right and wrong and the advice may make more sense.

Most of the time there are lots of ways to do things and there are lots of trade-offs, some humility when addressing others is a useful skill and you will very rarely know for sure that you are right and the other person is entirely wrong.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: