3 ms·
This feels like the intersection of a technology problem and a communication problem. What do you do when someone says something that is technically wrong? I un
by jergason 15y ago
This feels like the intersection of a technology problem and a communication problem. What do you do when someone says something that is technically wrong? I understand not wanting to embarrass someone else, but I also see Yehuda's point of view. People will be worse off if they do bad things in their code, so the best time to correct misinformation may have been right then, when everyone who heard it was still all together.
Maybe it could have been done with more tact, but I don't see it as heckling. You can attack someone's ideas without attacking the person. The less tied up you are to being right, the more open you are to criticism taking it personally, the more likely you are to learn something new.
- slantyyz 15y agoFeels more like a problem of simple manners to me. The easy and proper thing to do for Katz is simply take notes and wait until the end of the presentation to make his counter points during the q/a session. Interrupting someone in the middle of a presentation just makes it harder for the speaker to continue. The speaker is going to be more flustered and the flow and presentation will quickly degrade because he/she is going to be second guessing everything that he/she was going to say. For some speakers, one heckle turns them from an OK speaker to a bumbling mess. It's also going to have a chilling effect on the user group. Who's going to want to volunteer to do a presentation after this?