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.
Why you shouldn't invite Yehuda Katz to your user group meeting
11–20 of 108 posts
Re: Why you shouldn't invite Yehuda Katz to your user group meeting
#12That said, this story doesn't have the right context, ignoring the actual talk and the actual arguments brought by Katz. Maybe the mistakes done by the speaker were too great to be ignored - and this is very unlike the Dale Carnegie story quoted in the article, because such presentations are attended by people that want to learn something.
I have been feeling embarrassed myself when other people corrected me in public and it feels awful, however it's a lot better to accept and acknowledge valid criticism and valid counter arguments and actually thank the person that stood up to you, because you know, you learned something new.
Re: Why you shouldn't invite Yehuda Katz to your user group meeting
#13Wow. A post about etiquette that calls someone out by name, with an insulting headline? Face-to-face is the right channel for this sort of pointed criticism. Failing that, email might work. To pass the lesson along to the larger community, leave the specific names out of it - talk about "a big name in the community" who behaved badly. People who were there will know who you're talking about, but it doesn't become par…
Re: Why you shouldn't invite Yehuda Katz to your user group meeting
#14Wow. A post about etiquette that calls someone out by name, with an insulting headline? Face-to-face is the right channel for this sort of pointed criticism. Failing that, email might work. To pass the lesson along to the larger community, leave the specific names out of it - talk about "a big name in the community" who behaved badly. People who were there will know who you're talking about, but it doesn't become par…
Re: Why you shouldn't invite Yehuda Katz to your user group meeting
#15Generally, questions come in three classes: clarification ("I'm not sure I understand, can you explain..."), discussion ("Have you considered extending this to..."), and criticism ("I think there is a problem with this approach..."). In an academic setting, all are welcome unless otherwise stated. (Sometimes we say no discussion and critical questions because of time limitations.)
However, what is never acceptable is someone commandeering the presentation and using it to talk about their own thing. Moderators will step in if it starts devolving like that.
So, simply, you need to let your audience know what the format is, because had I been in your audience, I may have asked questions, too.
Re: Why you shouldn't invite Yehuda Katz to your user group meeting
#16Was Katz right?
We need more context, and we need less emotional argument. If the original presenter could effectively support his position then he would not have left the stage. And I would hope that Katz would not commit such a social atrocity without a very, very good reason. I don't find it hard to believe that the actual story is much more tame and logical than the author of this article thinks it is.
Re: Why you shouldn't invite Yehuda Katz to your user group meeting
#17I'm all for speaking your mind in public, and standing up for an opinion, but timing is everything. Yehuda Katz has poor timing.
Re: Why you shouldn't invite Yehuda Katz to your user group meeting
#18Dear Ruby "community", no-one cares about your internal bickering. Much as I hate to admit it, Zed Shaw was right.
The only thing I took away is: don't waste energy reading this.
Re: Why you shouldn't invite Yehuda Katz to your user group meeting
#19This is basically to well-actually an entire presentation. http://tirania.org/blog/archive/2011/Feb-17.html
Re: Why you shouldn't invite Yehuda Katz to your user group meeting
#20A bit more context wouldn't hurt. You don't want attendees, who don't know any better, to adopt really bad practices. For example, what if this was the context: sql = "select * from users where id = #{params[:id]}" Although even here there's a right and a wrong way to approach this.