Ponderable: disciplinary specific data about questions at professional conferences.

This week I’m attending the annual meeting of the Pacific Division of the American Philosophical Association in San Francisco. There are lots of interesting talks on the program, but I find myself noticing some of the habits of philosophers that are on display in the question-and-answer periods at the end of the talks.

For example, philosophers seem to have a hard time asking a concise question. It’s not obvious that this is always a problem — providing a bit of context with the question can make it easier to get an answer to the question one is trying to ask — but sometimes the queries come with so much background that it’s hard to identify the actual question. And sometimes it’s just that the questioners are just trying to ask too many things at once. (To be fair, some philosophers recognize this, including one this morning who started, “I have two questions, but I’ll try to reduce them to a single one …”) Then too there are the questioners disinclined to yield the floor, persisting with follow-up queries even as the session chair is indicating that they should shut up so other people can get their questions answered.

My impression is that some of these behaviors are generational (or maybe related to status within the professional community), but others strike me as behaviors characteristic of philosophers.

Are there patterns of engagement in professional meeting Q&A that you take to be distinctive of your discipline? Any behaviors you think are dying out, or surging forth? And, if you’re one of those interdisciplinary creatures, are there exotic Q&A behaviors you notice when you go to professional meetings with folks from the other side of a disciplinary fence?

(I’m now thinking I might start collecting some more precise data on questions for the remainder of the meeting, to see how measurements square with my impressions.)

I don’t know and I don’t care: ignorance, apathy, and reactions to exposure of bad behavior.

I’ve already shared some thoughts (here and here) on the Adria Richards/PyCon jokers case, and have gotten the sense that a lot of people want to have a detailed conversation about naming-and-shaming (or calling attention to a problematic behavior in the hopes that it will be addressed — the lack of a rhyme obviously makes this more careful description of what I have in mind less catchy) as a tactic.

In this post, I want to consider how ignorance or apathy might influence how we (as individuals or communities) evaluate an instance of someone calling public attention to a microaggression like a particular instance of sexual joking in a professional environment.

It has become quite clear in discussions of Adria Richards and the PyCon jokers that, for any particular joke X, there are people who will disagree about whether it is a sexual joke. (Note that in the actual circumstances, there was agreement between Adria Richards, the PyCon jokers, and the PyCon staff that the jokes in question were inappropriate — and also significant, if not total, agreement from “mr-hank,” who claims to be the PyCon joker who was fired, that some of the jokes in question were sexual.) Let’s posit, for the purposes of this discussion, a case where there is no disagreement that the joking in question is sexual.

So, you’re with others in a work environment (like audience seating for a presentation at a professional conference). You are in earshot of a sexual joke — maybe as part of the intended audience of the joke teller, maybe not, but certainly close enough that the joke teller has a reasonable expectation that you may hear the joke correctly (which you do). Do you call the attention of the community to the sexual joking and the people engaging in it?

One reason to point out the microaggression is to address ignorance.

The people engaged in the sexual joking may not realize that they are doing something inappropriate in a professional environment. This lack of knowledge may require a serious commitment — for example, not to read conference codes of conduct, not to absorb any workplace anti-harassment training — but I suppose it’s not impossible. So, pointing out to individual jokers, “Dude, that’s inappropriate!” might reduce the ignorance of those individuals. It might also reduce the ignorance of the silent bystanders also in earshot of the sexual joking.

Drawing attention of the larger community to the particular instance of sexual joking may help dispel the ignorance of that larger community (and of its individual members, including those not in earshot of the joking), establishing the existence of such microaggressions within the community. If members of the community make a habit of pointing out each such microaggression they observe, it can also help the community and its members get good information about the frequency of behavior like sexual joking within the professional environment of the community.

Pointing out the microaggression, in other words, can help the community to know that microaggressions are happening, how frequently they’re happening, and who is committing them. The hope is that having good knowledge here is more likely to lead to an effective response to the problem than ignorance would be.

There are other dimensions of ignorance you might want to address — for example, whether people within the community experience discomfort or harm because of such microaggressions, or what empirical studies show about whether sexual joking in the workplace is harmful regardless of whether members of the community report that they enjoy such joking. Still, the thought here is that identifying facts is the key to fixing the problem.

However, you might not think that ignorance is the problem.

It might be the case that the people telling the sexual jokes are fully aware that sexual joking is inappropriate in a professional environment — that what they’re doing is wrong.

It might be the case that the larger community is fully aware of the existence of microaggressions like sexual joking in their professional environments — and even fully aware of the frequency of these microaggressions.

In these circumstances, where ignorance is not the problem, is there any good reason to point out the microaggression?

Here, the relevant problem would seem to be apathy.

If the community and its members have good information about the existence of microaggressions like sexual joking in their professional environments, good information about the frequency of such microaggressions, even good information about which of its members are committing these microaggressions and still cannot manage to address the problem of eliminating or at least reducing the microaggressions, you might be pessimistic about the value of pointing out another instance when it happens. Reluctance to use good information as the basis for action suggests that the community doesn’t actually care about the well-being of the members of the community who are most hurt by the microaggressions, or doesn’t care enough about the harm caused by the microaggressions to put the effort in to doing something about them.

(Those silent bystanders also in earshot of the microaggressions? If they aren’t ignorant about what’s happening, its inappropriateness, and the harms it can do, they are letting it happen without making any effort to intervene. That’s apathy in action.)

But perhaps it is possible, at least some of the time, to shake a community out of its apathy.

Sometimes bringing a microaggression to the community’s attention is a way to remind the community that it is not living up to its professed values, or that it is allowing some of its members to be harmed because it won’t ask other members to take a bit more effort not to harm them.

Sometimes reporting the microaggressions forces members of a community to reconcile what they say they are committed to with how they actually behave.

Sometimes exposing microaggressions to the view of those outside the community brings external pressure upon the community to reconcile its walk with its talk.

It’s looking to me like calling attention to a microaggression — sometimes attention of individuals committing it, sometimes attention of the community as a whole, sometimes the attention of those outside the community who might put pressure on the community and its members — has promise as a tactic to dispel ignorance, or apathy, or both.

In the case that microaggressions are recognized as actually harmful, what’s the positive argument against exposing them?

Naming, shaming, victim-blaming: thoughts on Adria Richards and PyCon.

By now many of you will have heard the news about Adria Richards attending PyCon, notifying the conference staff about attendees behind her telling jokes during a conference presentation (about, among other things, making the coding community more welcoming for women and girls). Richards felt the jokes were sexualized enough to harm the environment of the conference. PyCon had a Code of Conduct for the conference that encompassed this kind of issue. In a room with hundreds of attendees, in a context where she hoped this harm to the conference community would be dealt with rather than let go (which gives it tacit approval) but where she also didn’t want to disrupt the presentations underway, Richards took a picture of the men telling the sexualized jokes and tweeted it with the conference hashtag to get the conference staff to deal with the situation.

The conference staff addressed the issue with the men telling the jokes. Subsequently, one of them was fired by his employer, although it’s in no way clear that he was fired on account of this incident (or even if this incident had anything to do with the firing); Adria Richards started receiving an avalanche of threats (death threats, rape threats, we-know-where-you-live threats, you-should-kill-yourself threats); Adria Richards’ employer fired her; and PyCon started tweaking its Code of Conduct (although as far as I can tell, the tweaking may still be ongoing) to explicitly identify “public shaming” as harmful to the PyCon community and thus not allowed.

So, as you might imagine, I have some thoughts on this situation.

My big-picture thoughts on naming and shaming are posted at my other blog. This post focuses on issues more specific to this particular incident. In no particular order:

1. There is NOTHING a person could do that deserves to be met with death threats, rape threats, or encouragement to kill oneself — not even issuing death threats, rape threats, or encouragement to kill oneself. Let’s not even pretend that there are circumstances that could mitigate such threats. The worst person you know doesn’t deserve such threats. Making such threats is a horrible thing to do.

2. People disagree about whether the joking Adria Richards identified as running afoul of the PyCon Code of Conduct was actually sexual/sexist/inappropriate/creating a climate that could be hostile or unwelcoming to women. (A person claiming to be the joker who was subsequently fired seems to be ambivalent himself about the appropriateness of the joking he was doing.) But it’s worth remembering that you are a good authority on what kind of conduct makes you feel uncomfortable or unwelcome; you are not automatically a good authority on what makes others feel uncomfortable or unwelcome. If you’re a social scientist who has mounted a careful empirical study of the matter, or if you’re up on the literature describing the research that has been done on what makes people comfortable or uncomfortable in different environments, maybe you have something useful to add to the conversation. In the absence of a careful empirical study, however, it’s probably a good idea to listen to people when they explain what makes them feel uncomfortable and unwelcome, rather than trying to argue that they don’t actually feel that way, or that they’re wrong to feel that way.

In other words, that certain jokes would not have been a big deal to you doesn’t mean that they could not have had a significant negative impact on others — including others you take to be members of your community who, at least officially, matter as much as you do.

3. So, if Adria Richards was bothered by the joking, if she thought it was doing harm and needed to be nipped in the bud, why couldn’t she have turned around and politely asked the men doing the joking to knock it off? This question assumes that asking nicely is a reliably effective strategy. If this is your default assumption, please [I just noticed myself typing it as a polite request, which says something about my socialization as a female human, so I’m going to let it stand] cast your eyes upon the #Iaskedpolitely hashtag and this post (including the comments) to get some insight about how experience has informed us that asking politely is a pretty unreliable strategy. Sometimes it works; sometimes, buying a lottery ticket wins you some money. On a good day, politely asking to be treated fairly (or to be recognized as a full human being) may just get you ignored. On a not as good day, it gets you called a bitch, followed for blocks by people who want to make you feel physically threatened, or much, much worse.

Recognize that the response that you expect will automatically follow from politely asking someone to stop engaging in a particular behavior may not be the response other people have gotten when they have tried the approach you take as obviously one that would work.

Recognize that, especially if you’re a man, you may not know the lived history women are using to update their Bayesian priors. Maybe also recognize, following up on #2 above, that you may not know that lived history on account of having told women who might otherwise have shared it with you that they were wrong to feel the way they told you they felt about particular situations, or that they couldn’t possibly feel that way because you never felt that way in analogous situations. In other words, you may have gappy information because of how your past behavior has influenced how the women you know update their priors about you.

I try to recognize that, as a white woman, I probably don’t really grasp the history that Adria Richards (as a woman of color) has used to update her priors, either. I imagine the societal pressure not to be an “uppity woman” falls with much, much more force on an African American woman. Your data points matter as you plot effective strategies with which to try to get things done.

3.5. An aside: About a month ago, my elder offspring was parked in front of her laptop, headset on, engaged in an online multiplayer game of some sort. As the game was underway, one of the other players, someone with whom she had no acquaintance before this particular gaming session, put something pornographic on the screen. Promptly, she said into her headset mic, “Hey, that’s not cool. Take the porn down. We’re not doing that.” And lo, the other player took the pornographic image off the screen.

I was pretty impressed that my 13-year-old daughter was so matter-of-fact in establishing boundaries with online gamers she had just met.

I thought about this in the context of #Iaskedpolitely. Then I realized that I maybe didn’t have all the relevant information, so today I asked.

Me: That time you were online gaming and you told the other player to take down the porn? Is it possible the other player didn’t know you were a girl?

Her: Not just possible.

My daughter has a gender-neutral username. Her voice is in a low enough register that on the basis of her voice alone you might take her for a 13-year-old boy. This may have something to do with the success of her request to the other player to take the porn off the screen in the game.

Also, she didn’t bother with the word “please”.

In the three-dimensional world, where it’s less likely she’ll be assumed to be male, her experiences to date have not departed nearly as much from what you can find in #Iaskedpolitely as a mother would like them to.

4. Some of the responses to the Adria Richards story have been along the lines of “A convention or professional conference or trade show is totally not the same thing as a workplace, and it’s a Bad Thing that organizers are trying to impose professional-environment expectations on attendees, who want to hang out with their friends and have fun.” I’ll allow that even a professional conference is different from work (unless, I guess, your entire job is to coordinate or do stuff at professional conferences), but in many cases such a conference or convention or trade show is also still connected to work. One of the big connections is usually the community of people with which you interact at a conference or convention or trade show.

Here’s a good operational test: Can you totally opt out of the conferences or conventions or trade shows with no resulting impact on your professional life (including your opportunities for advancement, networking, etc.)? If not, the conferences or conventions or trade shows are connected to your work, and thus it’s appropriate to expect some level of professionalism.

None of which is to say that conventions one goes to off the clock, for fun, should necessarily be anarchic events, red in tooth and claw. Unless that’s how the community at that particular con decides it wants to have fun, I suppose.

Also, this is not to say that companies should necessarily fire their employees for any and every infraction of a conference Code of Conduct. Depending on what kind of violation (and what kind of ongoing pattern of problematic behavior and failed attempts at remediation an employee might have displayed) firing might be the right call. I have seen none of the personnel files of the persons directly involved in this case — and you probably haven’t, either — so the best I could do is speculate about whether particular firings were warranted, and if so, by what. I’m in no mood for such speculation.

5. On the matter of tweeting a photo of the PyCon attendees who were telling the jokes Adria Richards felt were inappropriate in the circumstances: Lots of people have decried this as a Very Bad Way for Richards to have communicated to the conference staff about bad-behavior-in-progress with which she felt they should intervene. Instead, they say, she should have had a sense of humor (but see #2 above). Or, she should have turned around and politely asked them to cut it out (but see #3 above). Or, that she should have done something else. (Email conference staff and hope someone was monitoring the inbox closely enough to get promptly to the location ten rows back from the stage so that Richards could point the jokers out in a room with hundreds of people? Use a Jedi mind trick to get them to stop quietly?)

She alerted the conference staff to the problem via Twitter. She made the call, given the available options, the fact that she didn’t want to generate noise that would disrupt what was happening on the stage, and probably her judgments of what was likely to be effective based on her prior experiences (see #2 above).

Maybe that’s not the call you’d make. Maybe the strategy you would have tried would totally have worked. I trust you’re prepared to deploy it next time you’re at a conference or convention or trade show and in earshot of someone behaving in a way likely to make members of the community feel uncomfortable or unwelcome. I hope it’s just as effective as you imagine it will be.

Even if Adria Richards was wrong to tweet the picture of the jokers, that doesn’t mean that their joking was appropriate in the circumstances in which they were doing it at PyCon. It wouldn’t mean that the conference staff would be wrong to investigate the joking and shut it down (and deal with the jokers accordingly) if they judged it in violation of the Code of Conduct.

Also, one of the big complaints I’ve seen about the tweeted photo of the PyCon jokers is that using Twitter as a tool to report the problem removes the confidentiality that ought to accompany allegations of violations of the Code of Conduct, investigations of those allegations, penalties visited on violators, etc.

There’s a couple things I want to say to that. First, dealing with bad behavior “privately” (rather than transparently) doesn’t always inspire confidence in the community that the bad behavior is being taken seriously, or that it’s being addressed consistently (as opposed to, say, being addressed except when someone we really like does it too), or that it’s being addressed at all. Especially when the bad behavior in question is happening in a publicly observable way, taking the response completely private may be nearly as harmful to the community as the bad behavior itself.

Second, shouldn’t the people who want us to trust that the PyCon staff would have dealt with the PyCon jokers fairly and appropriately in private themselves trust that the PyCon staff had addressed any violation of the conference Code of Conduct Adria Richards might have committed by tweeting the picture of the PyCon jokers (rather than emailing it or whatever) — and that they’d dealt with such a violation on Richards’ part, if they judged it a violation, in private?

There’s just a whiff of a double standard in this.

6. On the post-conference update to the PyCon Code of Conduct to to explicitly identify “public shaming” as harmful to the PyCon community and thus not allowed: I’m hopeful that PyCon organizers take account of the effects on the community they have (and on the community they are trying to build) of opacity in dealing with bad behavior versus transparency in dealing with bad behavior.

It’s not like there isn’t already reason to believe that sometimes conference organizers minimize the impact of instances of harassment reported to them, or deny that any harassment has been reported at all, or back off from applying their own explicit rules to people they judge as valuable to the community.

These kinds of actions may harm their community just as much as public shaming. They communicate that some harassers are more valuable to the community than the people they harass (so maybe a bit of harassment is OK), or that people are lying about their actual experiences of bad behavior.

7. There has been the predictable dissection of Adria Richards’ every blog post, tweet, and professional utterance prior to this event, with the apparent intention of demonstrating that she has engaged in jokes about sex organs herself, or that she has a history of looking for things to get mad about, or she’s just mean, and who is she to be calling other people out for bad behavior?

This has to be the least persuasive tu quoque I’ve seen all year.

If identifying problematic behavior in a community is something that can only be done by perfect people — people who have never sinned themselves, who have never pissed anyone off, who emerged from the womb incapable of engaging in bad behavior themselves — then we are screwed.

People mess up. The hope is that by calling attention to the bad behavior, and to the harm it does, we can help each other do better. Focusing on problematic behavior (especially if that behavior is ongoing and needs to be addressed to stop the harm) needn’t brand the bad actor as irredeemable, and it shouldn’t require that there’s a saint on duty to file the complaint.

8. Some people have opined that it was bad for Adria Richards to call out the PyCon jokers (or to call them out in the particular way she did) on account of the bad consequences that might befall them if they were known to have violated the PyCon Code of Conduct. But the maxim, “Don’t call out bad behavior because doing so could have negative consequences for the person behaving badly” just serves to protect the bad behavior and the bad actors. Being caught plagiarizing can be harmful to a scientist’s career, so for heaven’s sake don’t report it! Being convicted of rape can end your future as a football player, so your victim ought to refrain from reporting it, and the authorities ought to make sure you’re not prosecuted!

Bad behavior has bad consequences, too.

The potential bad consequences of being caught behaving badly should, perhaps, help motivate people not to behave badly, especially in cases where the harms of that bad behavior to individuals or the community are not themselves sufficiently motivating to prevent the behavior.

9. Finally, some people have been expressing that it makes them feel uncomfortable and unwelcome when they are not allowed to act they way they want to, tell the jokes they feel like telling, and so forth.

I don’t doubt this for a minute.

However, this is not necessarily a bad thing. In the end, it comes down to a question of who you want in your community and who you want out of it. Personally, I don’t want my professional communities to be comfortable places for racists or sexists, for rapists, plagiarists, or jerks. Other people, I imagine, would prefer a professional community that’s a comfortable place for racists or sexists, for rapists, plagiarists, or jerks to a professional community that’s a comfortable place for me.

But here’s the thing: if you say you want your community to be welcoming to and inclusive of people who aren’t yet represented in great numbers, it might require really listening to what they say about what’s holding them back. It might require making changes on account of what they tell you.

It’s still possible that you’ll decide in the end to prioritize the comfort of the people already in your community over the comfort of the people you thought you wanted to welcome into your community. But in that case, at least have the decency to be honest that this is what you’re doing.

* * * * *

Also, pretty much everything Stephanie says here.

* * * * *

UPDATE: So, there are people who seem very eager to share their take on this situation (especially, for some odd reason, their autopsies of every wrong thing Adria Richards did) in the comments, but without engaging with anything I’ve written in the 3000 words here — including the things I’ve written here that directly address the points they’re trying to make.

There are many, many places on the internet where these not-really-engaging-with-the-conversation-we’re-having-here contributions would be welcome. But it’s probably worth updating some prior probabilities about whether those comments will make it out of moderation here.

#scio13 aftermath: some thoughts about the impostor syndrome.

I didn’t end up going to the Impostor Syndrome session at ScienceOnline 2013. I told myself this was because it would be more professionally useful to attend Life in the venn – What happens when you’re forced to wear many hats? since I have recently added a hat of my own (Director of my university’s Center for Ethics). But, if I’m honest with myself, it’s because I felt like too much of an impostor to contribute much of anything — even useful tweets — to the impostor syndrome session.

I have felt like an impostor since at least high school, and maybe before that.

I have known, since at least my second year of college, that the impostor syndrome was a real phenomenon. It was even the topic of my term paper in Psych 101. But knowing that the syndrome was a real thing, and that it involved a mismatch between one’s actual accomplishments and how accomplished one felt on the inside, didn’t make me feel like less of a fraud.

It probably goes without saying that I had a flare-up of the impostor syndrome in my first Ph.D. program. I had another flare-up in my second Ph.D. program (although I was maybe a little better at hiding my self-doubt). Going on the academic job market in philosophy made me feel like perhaps the biggest fraud of all … until I went up for tenure.

The frustrating thing about the impostor syndrome is that it makes it utterly impossible to tell whether your successes reflect any merit, or whether they are pure luck.

Whether the potential others see in you is real, and could somehow be converted to something of value (if only you manage not to blow it), or whether your only actual skill is talking a good game.

Whether piping up to share what feel like insights is reasonable, or whether you are just wasting people’s time.

I worry that what it might take to overcome my own impostor syndrome is an actual flight from reality. I know too many smart, accomplished people in my field who have not met with the recognition or success they deserve to believe we’re working within a pure meritocracy — which means it’s unreasonable for me to take my own success as a clear indicator of merit. I also know that past performance is not a guarantee of future returns — which means that even if I have done praiseworthy things in the past, I could blow it at any moment going forward.

And I also worry that maybe I don’t really have impostor syndrome, in which case, the reasonable conclusion, given how I feel a lot of the time, is that I actually am a fraud.

So, yeah, it’s one of those topics that feels very relevant, but is perhaps relevant enough that I’m not really in a good position to benefit from a discussion of it.

How’s that for a paradox?

* * * * *

Tweets from the Impostor Syndrome session have been Storified here.

#scio13 aftermath: synecdoche.

It seems inevitable that I come back from ScienceOnline conferences with an odd glow of enthusiasm which my colleagues want me to explain to them. What is this weird conference? Why does it attract such an odd array of researchers, educators, communicators, tool-builders, information curators, and science lovers? Are the conference-goers split off into their disciplinary tribes to focus just on the topic and initiative that are squarely in their wheelhouses?

With 10,000 words I’m not sure I could come close to explaining it. But as David Quammen pointed out when he spoke to us in a CONVERGE session, sometimes focusing on a piece of the experience, a part of the whole, can convey something more.

I had the pleasure of sitting right across the aisle from Jason Goldman on our short flight from Raleigh-Durham to Charlotte on Sunday, and he mentioned that he had captured a tiny bit of video that he was showing to folks to explain what ScienceOnline was like to them. He gave me permission to share that video here:

Science Online, Gangnam style

As a bit of background, Carin Bondar had launched a plan to create a music video to capture some sense of what it was like to be at ScienceOnline 2013. (She made one at ScienceOnline 2012 that was a big hit, so people were pretty enthusiastic to help.) This year’s effort sought (among other things) masses of conference attendees delivering something recognizable as “Gangnam Style” choreography. If you don’t know what that is, let me introduce you to pop phenomenon PSY:

PSY “Gagnam Style”

The mission: get an odd array of researchers, educators, communicators, tool-builders, information curators, and science lovers to dance like PSY.

Our sensei: John Rennie, esteemed former editor in chief of Scientific American, adjunct instructor in New York University’s Science, Health and Environmental Reporting Program, science writer, editor, and blogger.

John’s resume does not, as far as I can tell, include a stint as a dance instructor on a cruise ship or on land. However, when given the challenge of mastering some key choreography and of teaching it to a bunch of people (most of whom are not experienced dancers) on the spot, he attacked that challenge so earnestly that we were all committed.

We wanted to learn the steps. We believed we could figure them out, not just because we wanted to, but because John found a way to communicate them to us despite the fact that our entusiasm was much bigger that our talent. And by golly, we had an awesome time being part of the simultaneous transfer of skills and enthusiasm.

What happened that evening with a dance routine is not unrelated to what happens during the whole rest of the conference with our knowledge, our tools, our questions, our ideas for communication, for pedagogy, for outreach, for better ways of doing science, for better ways of sharing our world.

That’s not the whole of the ScienceOnline experience, but it’s an essential part of it, and it’s just as infectious as a pop song.

Dispatch from #scio13: Tweet me maybe?

So, last night at ScienceOnline there was an Open Mic Night, masterfully MC’d by Jacquelyn Gill and David Schiffman. There was a lot of talent on display, but also initial issues with the sound at the venue. (Scott Huler and Brian Malow were the committed empiricists who figured the issue out … it turned out something was plugged into the wrong hole. (Insert gratuitous punchline here.)) The evening culminated with a inspiring dance lesson from John Rennie, who is without a doubt the science journalist you want to teach you how to dance.

Anyway, as conveyed on the Twitters, I made the (almost surely ill-advised) decision to get up and sing at Open Mic Night. While I am pleased (and relieved) to report that I didn’t end up in the Shatner zone in the chorus, a sound engineering issue meant that I lost half of my first verse. So, here are the lyrics to my song about social media, set to a possibly recognizable tune. (If you don’t mind, imagine me singing it in tune.)

I threw a post on my wall,
Only been blogging since Fall,
Your “like” pleased me most of all,
And now you’re in my feed

I’d trade my soul for a link,
I’d kill to hear what you think,
I’d even write you with ink
‘Cause now you’re who I read

FriendFeed was slogging,
Tumblrs were reblogging,
G+ hangouts, I’m no quitter,
Mention me on Twitter, baby?

Hey, I just met you,
And this is crazy,
But here’s my handle,
So tweet me, maybe?

It’s hard to match your
Traffic baby,
But here’s my hashtag,
Retweet me, maybe?

Hey, I just met you,
And this is crazy,
But here’s my handle,
So tweet, maybe?

And all the other blogs,
Try to shake me,
But here’s my hashtag,
Retweet me, maybe?

My comment got voted down,
Emoticon was a frown :-(
You took my logic to town,
But still, you’re in my feed

I didn’t give up the ghost,
Redeemed myself the next post,
Got linklove, I shouldn’t boast,
But it’s what I need.

Bora Z retweeted,
Ed Yong said to read it,
SiteMeter ebb and flowing,
Holy crap I’m linked on BoingBoing!

Hey, I just met you,
And this is crazy,
But here’s my handle,
So tweet me, maybe?

It’s hard to match your
Traffic baby,
But here’s my hashtag,
Retweet me, maybe?

Hey, I just met you,
And this is crazy,
But here’s my handle,
So tweet, maybe?

And all the other blogs,
Try to shake me,
But here’s my hashtag,
Retweet me, maybe?

Before this ScienceOnline
My stats were so bad
My stats were so bad
My stats were so, so bad

Before this ScienceOnline
My stats were so bad
And you should know that
My stats were so, so bad

It’s hard to match your
Traffic baby,
But here’s my hashtag,
Retweet me, maybe?

Hey, I just met you,
And this is crazy,
But here’s my handle,
So tweet, maybe?

And all the other blogs,
Try to shake me,
But here’s my hashtag,
Retweet me, maybe?

Before this ScienceOnline
My stats were so bad
My stats were so bad
My stats were so, so bad

Before this ScienceOnline
My stats were so bad
And you should know that

So tweet me, maybe?

Ponderable: Academic hiring and interviewing.

It has been eleven years since I was last on the market for an academic job, and about six years (if I’m remembering correctly) since I was last on a search committee working to fill a tenure-track position in my department. Among other things, this means that I can consider the recent discussion of “conference interviews” at The Philosophy Smoker with something approaching “distance”.

However, as I’m well aware, distance is not the same as objectivity, and anyway objectivity is not the kind of thing you can achieve solo, so I’m going to do a little thinking out loud on the screen in the hopes that you all may chime in.

The nub of the issue is how search committees in philosophy (and in at least some other academic disciplines) use preliminary interviews (typically 30 to 60 minutes in length) to winnow their “best” applicants for a position (as judged on the basis of writing samples, publication records, letters of recommendation, transcripts, teaching evaluations, and other written materials) down to the finalists, the number of which must be small enough that you can reasonably afford to bring them out for campus interviews.

The winnowing down is crucial. From more than a hundred applications, a search committee can usually reach some substantial agreement on maybe twenty candidates whose application materials suggest the right combination of skills (in teaching and research, and maybe also skills that will be helpful in “service” to the department, the institution, and the academic discipline) and “fit” with the needs of the department (as far as teaching, advising students, and also creating a vibrant community in which colleagues have the potential for fruitful collaborations close at hand).

But even if we could afford to fly out 15 or 20 candidates for campus interviews (which typically run a day or two, which means we’d also be paying for food and lodging for the candidates), it would literally break our semester to interview so many. These interviews, after all, include seminars in which the candidates make a research presentation, teaching demonstrations (hosted in one of our existing classes, with actual students in attendance as well as search committee members observing), meetings with individual faculty members, meetings with deans, and a long interview with the whole search committee. This is hard enough to squeeze into your semester with only five candidates.

So, the standard procedure has been to conduct preliminary interviews of shorter duration with the 20 or so candidates who make the first cut at the Eastern Division Meeting of the American Philosophical Association. For departments like mine, these interviews happen at a table in a ballroom designated for this purpose. Departments that have a bit more money will rent a suite at the conference hotel and conduct the interviews there, with a bit less background noise.

Job candidates pretty much hate this set up. The conference falls during winter holidays (December 26-30 or so), which means travel is more expensive than it might be some other time of year. Search committees sometimes don’t decide who they want to interview at the convention until quite late in the game, which means candidates may not hear that a department would like to interview them until maybe a week before the conference starts (boosting the price of those plane tickets even more, or making you gamble by buying a plane ticket in advance of having any interviews scheduled). Even at conference rates, the hotel rooms are expensive. Occasionally, winter storms create problems for candidates and search committee members try to get to, or to flee from, the conference. Flu season piles on.

Search committee members are not wild about the logistics of traveling to the convention for the interviews, either. However, they feel like the conference interviews provide vital information in working out which of the top 20 or so candidates are the most likely to “fit” what the department wants and needs.

But this impression is precisely what is in question.

It has been pointed out (e.g., by Gilbert Harman, referencing research in social psychology) that interviews of the sort philosophy search committees use to winnow down the field add noise to the decision process rather than introducing reliable information beyond what is available in other application materials. This is not to say that search committees don’t believe that their 30 or 60 minutes talking with candidates tells them something useful. But this belief, however strong, is unwarranted. The search committee might as well push itself to identify the top five candidates on the basis of the application materials alone, or, if that’s not possible, randomly pick five of the top twenty for campus interviews.*

Of course, search committees seem not to be in a great hurry to abandon conference interviews, at least in philosophy. My (brief) experience on the scientific job market didn’t include conference job interviews per se, but I did have preliminary interviews of very much the same nature and duration with some private sector companies and national labs — which is to say, I don’t think it’s just philosophers who are making hiring decisions that are at least partially grounded on a type of information we have reason to believe could be misleading.

The question, of course, is what to do about all this.

Search committees could abandon these preliminary interviews altogether. That would surely put more pressure on the written components of the applications, some of which might themselves be misleading in interesting ways. I’m guessing search committees would resist this, since they believe (although mistakenly, if the research is right) that they really are learning something important from them. It’s not obvious to me that job candidates would unanimously endorse this either (since some see the interview as a chance to make their case more vividly — but again, maybe what they’re making is pseudo-evidence for their case).

Search committees could work to structure preliminary interviews so that they provide more reliable information (as the research suggests properly structured interviews actually do).** This would require search committee members to learn how properly to conduct such interviews (and how properly to record them for later examination and evaluation). Moreover, it would require that search committee members do something like acknowledging that their instincts about how to conduct free-flowing, open-ended preliminary interviews that are also informative are probably just wrong. This is a task with a difficulty level that’s probably right around what it takes to get science faculty to acknowledge that having learned a lot about their field might not be sufficient to be able to teach it effectively, and that science education research might be a useful source of empirically grounded pedagogical insight. In other words, I think it would be really hard.

Search committees could keep conducting preliminary interviews as they always have. Inertia can be powerful, as can the feeling that you really are learning something from the interviews. However, it seems like a search committee would have to take into account the claim that, empirically, interviews are misleading when drawing conclusions on the basis of preliminary interviews. (Of course this is a normative claim — the search committees ought to take this worry into account — rather than a claim that mere exposure to a research finding would be enough to remove the search committee’s collective powers of self-delusion.)

Or … search committees could do something else?

What else could they do here? How do those of you in scientific fields handle the role of interviewing in hiring? Specifically, do you take concrete measures to ensure that interviews don’t introduce noise into hiring decisions? Or do you feel that the hiring decisions you need to make admit of sufficiently objective information that this just isn’t a problem for you?

If you prefer to comment pseudonymously for this discussion, feel free, but one pseudonym to a customer please.

_____
* For all I know, campus interviews may introduce some of the same kinds of noise to the decision-making process as conference interviews do. However, many include teaching demonstrations with a sample from the actual student population the candidate would be asked to teach if hired, a formal presentation of the candidate’s research (including responding to questions about it), and ample opportunity for members of the hiring department to get a sense of whether the candidate is someone with whom one could interact productively or instead someone who might drive one up a wall.

** It is worth noting that some search committees, even in philosophy departments, actually do conduct structured interviews.

To tweet or not to tweet the professional conference? (Some thoughts in 140-character chunks.)

There’s a lot of discussion kicking around the tubes at the moment about whether it is appropriate to live-tweet a session at a professional conference. The recent round of discussion looks to have originated among English faculty. At the blog Planned Obsolescence, The Modern Language Association’s Director of Scholarly Communication, Kathleen Fitzpatrick, offers sensible advice on tweeting or not at meetings. Meanwhile Prof-like Substance is quizzical about the request to keep private what a scholar is presenting in the public space provided by a professional meeting (while recognizing, of course, that there are venues like Gordon Research Conference that have explicit rules about not publicizing what is presented beyond the bounds of the conference).

It’s no secret that I’ve tweeted a meeting or two in my time. I’ve even mused at some length about the pros and cons of tweeting a meeting, although mostly from the point of view of the meeting attendee (me) absorbing and interacting with what is being presented, compared to taking notes in my notebook instead.

If pressed for a blanket statement on whether tweeting a conference presentation is OK or not OK, I would say: it depends. There are complexities here, many linked to the peculiar disciplinary norms of particular professional communities, and given that those norms are themselves moving targets (changing in response to the will of active members of those communities, among other things), any ruling that somehow got it right at this moment would be bound for obsolescence before very long.

In other words, I don’t have a grand argument covering all the relevant contexts. Instead of trying to frame such an argument, I’m going to give you my thoughts on this, in tweet-sized bites:

  • Tweeting a meeting is a way to include members of the professional community who didn’t have the funds or flexibility to be there IRL.
  • Tweeting a meeting is a way to include interested people beyond the professional community in the audience and the discussion.
  • Since Twitter is interactive, tweeting a meeting is a way to promote discussion of what’s being presented RIGHT AWAY, for better or worse.
  • For worse: discussion may start before relevant facts, ideas are on the table, assuming things speaker isn’t claiming as speaker’s point.
  • For better: speaker can get rapid feedback on which points are persuasive, which seem iffy, as well as on fruitful tangents and connections.
  • Worry: conference tweeters distracted from engaging with speakers, people in room, & asking questions there. Some folks are not on Twitter!
  • Worry: conference tweeters may give inaccurate account of speaker’s claims, fail to distinguish their commentary from reporting of talk.
  • But, if multiple attendees tweet session, more basis to tease out which thoughts are from speaker, which from tweeters responding to talk.
  • Worry: live-tweeting sessions opens speakers to having results/ideas/arguments swiped by someone not at the meeting. Might get scooped.
  • Of course, others in the room could swipe speaker’s results/ideas/arguments. Why assume you couldn’t already get scooped?
  • Is community pressure stronger on people in the room (not to scoop speaker) than on members of the community following tweets? If so, why?
  • Live-tweeting meeting w/proper attribution of speaker could serve as record of results/ideas/arguments and who presented them. Protection!
  • Challenge to proper tweetribution of talk contents: getting speakers’ Twitter handles right. These could be listed in conference program.
  • Could be issues including speakers’ Twitter handles in tweets of their talks if their use of Twitter is primarily personal, not profesisonal
  • Some speakers freaked out by people tweeting their talks (especially in workshop-y/preliminary results scenarios). Should that be respected?
  • Are they also freaked out by people taking notes at their talks? Is worry sharing-beyond-room or rapid amplification potential?
  • Big Q: Does community view its professional meetings as public venues or something more limited? If latter, what is rationale for limits?
  • When meeting tweets help scholars figure something out, will they cite tweets? Easier than citing chat at hotel bar & easier to recall later
  • Expectations different in different disciplines; tweeting interdisciplinary conferences likely to expose differences in norms.
  • Never a bad idea to ask if speakers are OK with having their talks tweeted. If not, talking about why afterwards could be informative.
  • Things not to tweet (identifiably) from a talk: how bored you are, commentary on speaker’s looks. Save that for your notebook.
  • If tweeting conferences becomes a standard thing, might be tensions between “official” tweeters and independent attendee tweets.
  • Mass tweeting might also make serious bandwidth at conference venue a requirement. Expect that would increase registration fees!
  • Some fields likely to have harder time with 140 char limit than others. Push to be concise might be a positive influence on them.

I welcome your thoughts in the comments (and you can use more than 140 characters if you need to).

Looking ahead to #scio12: the nature of the unconference.

One of the things that makes ScienceOnline different from lots of other academic or professional conferences is that it is structured as an “unconference”. So … what exactly does that mean?

For one thing, it challenges the standard model of the expert at a podium at the front of the room, dispensing finished knowledge to the audience. The assumption is that the “audience” is really a group of interested participants who are bringing plenty of expertise to the table, and that they will be working together with the session moderator to figure new things out.

I’ve been to the rare academic conference with “workshop” sessions that achieve real engagement of, and participation from, nearly everyone in the room. At ScienceOnline, those levels of engagement and participation are not rare at all.

Some unconferences are so participant-driven that the program doesn’t even exist until the conference goers convene. Folks use whiteboards or paper to describe a session they want to happen (whether they have the expertise to lead it or are looking for other participants who could share that expertise), and ideas, people, spaces, and blocks of time are negotiated on the spot to build a program.

For those of us in disciplines where conference presentations usually flow from finished papers submitted a year in advance, this process can feel a little destabilizing. It’s not necessarily a bad thing.

The other unconference in which I’ve participated (She’s Geeky) has used this process. Along with it, the conference organizers provide reminders:

“Be prepared to be surprised!”

“Whoever comes is the right people. Whatever happens is the only thing that could have. Whenever it starts is the right time. When it’s over, it’s over.”

In other words, part of the point of having an unconference is to cultivate serendipity, to foster connections of ideas and people that can happen organically but that might not happen with too much rigid planning. Working this way has its risks. There may be only a handful of people interested in what you want to talk about, and what people have to say may fit in a non-standard time interval. But the risks are part of the deal to unlock the rewards.

There was another reminder, whose placard I managed not to photograph, of “The Law of Two Feet” — basically, that each participant should take responsibility for being where she wanted or needed to be, even if that meant leaving one group midway through or joining another already in progress, and that other participants should respect each individual’s decisions rather than expecting a captive audience. This strikes me as the right attitude to take to cope with a session which turns out to be not what you expected or wanted to be a part of, rather than complaining later, “That’s an hour of my life I’ll never get back.”

If you look at the ScienceOnline 2012 conference program as it’s shaping up, you’ll see that this is not a conference generating sessions on the spot each morning. Rather, there are multiple sessions in each time slot, each with a title, one or more moderators, and a description of the topics to be discussed. In other words, this is a relatively organized unconference.

My sense, though, is that even though the advanced planning that goes into the sessions seems to pull against the “un”-ness of the conference, it actually makes possible a lot more participant-steering of sessions to address things the people coming to the sessions want to talk about — burning questions they have, experiences or expertise they want to share, resources, applications, connections to other things they care about, what have you. One way this can happen is via session wiki pages. For example, I’m helping lead two sessions, one (with Amy Freitag) on “Citizens, experts, and science”, the other (with Christie Wilcox) on “Blogging Science While Female”. Those wiki pages are just calling out for ideas, questions, or useful links. (Your ideas, questions, or useful links! What are you waiting for?)

Indeed, this is not simply a matter of shaping an hour-long discussion at the conference, but of jumping into a conversation now. It’s not a conversation that has to end when the next session starts — or when the conference itself is over. Nor is is a conversation that’s restricted to the people who are physically in the room. You can be part of the conversation even without setting foot in North Carolina.

And this brings me to another way ScienceOnline strikes me as interestingly different from other conferences I’ve attended. At many of these conferences, sessions spill over to interesting discussions over drinks or meals. That happens at ScienceOnline, too — but unlike discussions at other conferences that recede into memory when you get home, the conversations at ScienceOnline have a better than even chance of being tweeted, liveblogged, or otherwise captured and signal-boosted, making it possible for us (and you, and anyone else who want) to come back to them and push them further until we (not our feeble memories) decide we’re done with them.

Packing for #scio12: plumbing the inky depths.

A bunch of ScienceOnline 2012 attendees will be spending the Friday afternoon of the conference on The ScienceOnline2012 Science of Ink Tour, graciously hosted by the Dogstar Tattoo Company and featuring a lecture by Carl Zimmer on the science of tattoos

Some of the participants in this tour will also be coming back with brand new ink, which means they will want to pack accordingly.

1. Your copy of Science Ink for autographing. There are likely to be copies of the book available for purchase on the tour, but lots of you inked-up scientists already have one. Sure, maybe Carl Zimmer will have a chance to inscribe your book for you. The real action, though, is going to be finding conference-goers whose tattoos are featured in Science Ink and getting them to sign the the pictures of their tattoos.

2. Ointment to apply to your new tattoo. A new tattoo needs a thin layer of ointment twice a day. While some prefer a concoction called “Tattoo Goo” that is reputed to smell like hippies, my tattoo artist recommends Aquaphor, which you may be able to find in a 0.35-ounce tube that is conveniently sized for travel.

3. Antibacterial liquid soap. New tattoos also need to be washed twice a day (before you apply the ointment), preferably with a liquid soap that contains an antibacterial agent like Triclosan. (The store brand at most national drugstore chains will have such an option.) Bringing a conference-sized supply in a 1-ounce travel container will probably get you through.

Not pictured: Artwork to show your tattoo artist. When you’re getting inked, a picture is worth a thousand words. Print that puppy out, full-sized if at all possible.

Not pictured: Cash for your tattoo. Most tattoo parlors are cash-only. If you want the body art, be sure to bring the legal tender.

4. A clean washcloth. Even if you’re sticking to the temporary tattoos at the conference, hygiene matters. Always apply them with a clean washcloth, and try not to use brackish water.