tim: Tim with short hair, smiling, wearing a black jacket over a white T-shirt (Default)
[personal profile] tim
Because I'm having a few moments of emo and angst about the difficulty of understanding Rust code that's recently been rewritten, as well as the eventual fate of seemingly every major project I undertake, instead of writing a daily blog post today I'm going to talk about something different. (After all, my blog is on Dreamwidth, not LiveJournal, so emo and angst shouldn't be the order of the day.)

I went to a Mozilla intern's final research talk today. It was a good talk, covering some impressive work. Here are some hints for people attending research talks. Actually, they're more like requirements than hints.

1. If the speaker answers a question in a way that you think is naïve, consider that you may have misunderstood what they said. It is always possible that you are wrong, and that what you think was an assertion of fact was actually intended as a hypothetical, simplifying assumption that the speaker does not actually think is true. Under no circumstances should you burst out laughing. Laughter has the tendency to get the rest of the room laughing too, whether or not they actually understood the reason for the laughter. At any rate, laughing at a speaker is really not appropriate under any circumstances unless they have just told a funny joke.

Even if you are friends with the speaker and think that your laughter is appropriate given the terms of your relationship, not everybody else in the audience knows that. Your behavior sets an example: in this case, that it's okay to laugh at people. It has an effect. Try to make it a good one.

2. If you have something snarky to say about the contents of a talk, say it to your friend afterward. Write it down, if that helps. Don't say it out loud during the talk, even if you think no one else can hear you. Always assume you're sitting next to the lead developer on the project that the speaker is speaking about, and that they have excellent hearing.

Respecting people isn't hard, but when people do stuff like this, it fosters a disrespectful culture. It also creates an environment where people are afraid to speak up, make mistakes, and be wrong. Everyone should be able to experiment, take risks, and express bold opinions without fear of being made fun of for not knowing something. When somebody needs to boost themself up at another person's expense, I always assume that they're deathly insecure and afraid of having their own ignorance exposed. But there's no need to be afraid. Building software is difficult, and nobody is naturally good at it. We can all build an environment where no one is afraid to expose their weaknesses -- which is to say, where no one is afraid to learn and grow.

(no subject)

Date: 2012-08-04 03:36 am (UTC)
dharma_slut: Delicate pink cherry bloosms say; "I am a fragile fucking flower" (speshul)
From: [personal profile] dharma_slut
Dude-- women aren't *people,* in tech. Everybody* knows that. Or wants to know that.

*For a certain definition of "everybody" EG "cis male brocoders"

But there's no need to be afraid. Building software is difficult, and nobody is naturally good at it.

Oh, snap!

(no subject)

Date: 2012-08-04 07:20 am (UTC)
luinied: Extra! Break the eggshell! Have you heard? (collected)
From: [personal profile] luinied
This is way funnier if you assume that brocorder = bro + vocorder.

(no subject)

Date: 2012-08-04 07:43 am (UTC)
dharma_slut: MiRaCLeS (MiRaCLeS)
From: [personal profile] dharma_slut
It would be even funnier if the all had little volume controls that went to minus 1.

(no subject)

Date: 2012-08-04 04:01 am (UTC)
synecdochic: torso of a man wearing jeans, hands bound with belt (Default)
From: [personal profile] synecdochic
Man, I wish we could, like, hand out those numbered paragraphs anywhere people are attending talks.

(no subject)

Date: 2012-08-04 07:18 am (UTC)
luinied: The robot catches many monkeys. (academic)
From: [personal profile] luinied
For the first part of #1 - and maybe I've said this before - I think I really benefited from all those talks with Benjamin Pierce in the audience. He obviously really, really knows what he's talking about when it comes to typed functional programming languages - and he subjects everyone's work to pretty exacting standards - but he always asks questions assuming that he's missed something, or that he isn't understanding the speaker or the paper well enough, or that he's otherwise confused. Not only is he an excellent role model in how to ask questions, but he seemed to really set a non-dickish tone for our whole group (though of course Steve and Stephanie deserve plenty of the credit for that as well) - my theory is that it's just harder to be arrogant and dismissive when the people in charge are so humble and generous.

(no subject)

Date: 2012-08-09 07:54 am (UTC)
ext_17921: (Default)
From: [identity profile] lindseykuper.livejournal.com
I noticed Benjamin doing this at OPLSS, which I just attended for the first time last month, and I appreciated it a lot!

(no subject)

Date: 2012-08-05 04:27 am (UTC)
From: [identity profile] anemone.livejournal.com
I get SO ANNOYED when we have a candidate and people ask inappropriate questions, eg "Isn't your model all wrong?"

It's reasonable to make sure you understand the model (depending on the audience size), so asking what the model is fine. And at the end of the talk, it's a probably good to question whether the model is realistic or why it was chosen. But it's derailing and pointless to ask a "but aren't all your assumptions wrong" question in the middle of the talk.

I'm lately trying to stop it those sorts of questions, but I'm neither social skilled nor powerful, so I'm not that good at it.

Profile

tim: Tim with short hair, smiling, wearing a black jacket over a white T-shirt (Default)
Tim Chevalier

September 2014

S M T W T F S
 1234 56
78 910 111213
1415 16 17 18 1920
21 22 23242526 27
282930    

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags