Skip to main content

Learning to love conferences

Jean Yang, Nadia Polikarpova, and Shachar Itzhaky recently put together a post giving advice to a first-time academic conference-goer. Looking at this advice from where I am now, as a semi-experienced academic with several conference communities I really love to be around, the advice resonates with me, to an extent: if I prepare well, a conference can be a great opportunity to extend the breadth of my network and find new collaboration opportunities.

But careful preparation and bold approaches of strangers were not, by a long shot, how I learned to enjoy conferences. And enjoyment was, for me, a crucial step to being good at them. I don't want to say you have to enjoy conferences in order to be good at them, but, since they are primarily social & emotional labor, sincerely enjoying yourself will make the job easier.

Personally, when I first received advice like Jean et al.'s as a new grad student, I had very bad experiences. I went in believing that I was all but disallowed from talking to people I already knew, and that the path to success was to go up to strangers I wanted to meet and try my hardest to impress them with my research. Here's the problem: I've struggled with social anxiety my entire life, and only started treating it several years in to grad school. So... the first several times I mentally prepared myself to approach someone and introduce myself at a conference, I had panic attacks -- shaking uncontrollably, difficulty breathing, nausea, &c. I stopped being functional at all and had to retreat to my hotel room to recover. Not the best way to make friends at a conference!

The few times I happened into conversations with new folks, as soon as my research came up, I felt so much pressure to impress that I did a terrible job of explaining it, and utterly failed to communicate excitement or interest in my work (or theirs), because there were so many negative feelings behind the activity I felt like I was trying to take part in. I came away from my first few conferences thinking, "Networking is just one of those necessary evils of academia, where everyone has to be fake to get ahead, and I'm never going to like it or be good at it."

Reflecting on the difference between this attitude and my current one wherein I look forward to conferences and find them energizing and inspiring, I can list a few things that seem like they played key roles. Of course, combating social anxiety should definitely include professional therapy if at all possible, which I've discussed in a prior post. But allow me to stick to the conference-specific points for this post.

  1. Acknowledging that conference anxiety is common was important for me -- hearing from my peers that they, too, find conferences exhausting and socially draining, helped me feel less alone. Realize that most folks who have a great deal of facility in a given conference environment have probably built up relationships with that community over several years, and don't expect yourself to have the same facility immediately. It's okay to be a newcomer, and it's okay not to be neurotypical.
  2. Going in with a cohort and/or a buddy that I could treat as "home base." Counter to the "don't talk to people you know" advice, I'd say it can actually be really important and helpful to do so -- not constantly, but simply as an anchor point. Have someone you can check in with to say "Hey, I just met [really famous researcher] and she was super nice to me! Do you want an introduction?" or "Wow, that person was kind of rude in Q&A, huh?" or whatever. Help each other out!

    As a personal concrete example: when I was first getting to know the games research crowd at FDG last year, being in a cohort of UCSC folks, who are well known as a group, and being able to introduce myself in relationship to them, was really enormously helpful in getting a foothold with strangers.
  3. Not being afraid to sacrifice breadth for depth. Sometimes it feels like you're not winning the conference game unless you're meeting as many people as possible, and during a great in-depth research discussion, it might be tempting to say "let's continue later, I need to circulate around the room." I've actually found it useful not to do this. As someone who tends to get more mileage out of few close connections than loads of shallow ones, allowing myself to really spend time with one or two new people has had a lot better future payoff.
  4. Posting to social media (in my case Twitter) has been a surprisingly effective way to make friends at conferences. Use the conference hashtag; post your notes or thoughts about a talk; check the hashtag yourself and reply to other people conversing. Often what happens is someone will ask to say hi to you in person if they'd like to talk in more depth about a comment you've made. I'm a lot more comfortable speaking my mind online, so this has been a great way to take advantage of my current comfort zone in order to expand it.
  5. On the hallway track: a common adage about conferences is that they're "mostly about the hallway track" and "the talks are less important than the people." I agree, but it took me a long time to get there, and when I first started out, I wasn't really sure how to apply this advice, because I'd often waste the hallway tracks standing around awkwardly with no one to talk to. Then, at lunchtime or whatever, someone would ask a question about that one great talk and I'd have nothing to say because I had skipped it. As a newer member of a community, I've found splitting talk/hallway track more like 70/30 (rather than my typical 30/70 these days) to be beneficial. And be sure to ask any senior members of the community you know which talks are not to be missed. (As a general rule, don't skip keynotes).
  6. Finding my people in sometimes-arbitrary ways can be helpful. For example, if the catered lunch isn't vegetarian friendly, asking a group (online or otherwise) who wants to go visit the nearest Indian restaurant/Chipotle/fancy local vegan place can be a great way to carve a subset of people with whom you immediately have a common discussion topic. Doing this by research interest -- e.g. at FDG, my roommate and I organized a "computational narrative" informal birds-of-a-feather meetup -- can be even better. (See point 2: having a "partner in crime" to help you spearhead things like this can be super useful!)
  7. Giving myself room to acknowledge and care for my needs has probably been the most critical change in behavior for being happy at conferences. At literally every conference, even now, I pick 1 or more sessions to skip just to do whatever feels most comforting to myself: lying in my hotel room with a book, sitting in a park, working out, grabbing tea with a close local friend, even just camping somewhere inconspicuously adjacent to the conference with my laptop and working on some research code or reading Twitter. It's really, really okay to disengage to whatever extent you need to, and it's been crucial for helping me conserve energy to keep being socially involved throughout longer conferences.

On the conference organization side, here are some things your committee can do to help guests with (my particular flavor of) social anxiety feel more comfortable and welcomed:

  1. Host the conference either in, or very close to, the hotel(s) where folks are staying so that it's easy to get back to your room.
  2. Host the conference somewhere in an environment where it's easy to get away for short durations: an urban environment, a campus with public spaces, or somewhere close to good transit options.
  3. Have a quiet room.
  4. To the extend that budget allows, do catered or otherwise on-site lunches (taking care to accommodate a wide range of diets!). It avoids awkward "will the team captain pick me last" situations where people have to self-organize into meal groups.
  5. Do some (optional) group off-site activities like hikes or board game nights, which allows folks to interact in a more casual, low-stakes environment if they wish.
  6. Hold post-talk discussions in their own room rather than doing Q&As, so that even those who are nervous about talking in front of large groups of people can have their thoughts about a talk heard. (Bonus: this saves time in the talk schedule!)
  7. Have a mentoring workshop or doctoral consortium to help acclimate junior researchers to the conference environment and provide a space for asking "beginner questions."
  8. Especially for the mentoring activities noted in (7), but also just in general, do all the usual things for ensuring you have a diverse line-up of conference speakers and leadership. There's nothing like being not only a brand-new member of a community with few connections but also feeling like a total outsider in terms of your core identity.


  1. Nice one, thanks for posting!

    Examples from my experience:

    6 ("finding your people"): once I found folks who like running as me, and we went for a run -- that was so cool!

    7 ("disengage"): listening and seeing so many external people mutes my inner voice. Disengaging helps to return to the balance (and hear it again!).

    As for the organization part -- yes, quiet room works:
    we once had a room, where people could sit till late evening and work. Some people occasionally talk -- and i could add a word naturally (without all those "approach a circle, introduce yourself").

  2. This comment has been removed by the author.

    1. This comment has been removed by the author.

  3. Interesting...

    It's like school or university. It's useless, it takes your time, it gives you nothing, but...
    You can make a lot of friends who were dumb enough to attend it like you did!

    Not a joke, actually, sad experience.


Post a Comment

Popular posts from this blog

Using Twine for Games Research (Part II)

This preliminary discussion introduced my thoughts on using Twine as a tool for creating prototypes for games research. I'll start with documenting my first case study: a hack-and-slash RPG-like setting where the player character has a record of attributes ("stats") that evolve through actions that turn certain resources (money, health, items) into others. I've selected this hack-and-slash example because it falls outside the canonical "branching story" domain thought to be Twine's primary use case, but it is not too much trickier to implement. It relies crucially on the management of state in ways that simple branching stories would not, but it does so in a fairly straightforward way.

If all goes well, this post may also serve as a tutorial on the "basics" of Twine (links + variables + expressions). In particular, I'll be using Twine 2/Harlowe, and I haven't seen many tutorials for this new version published yet.

To me, the main "…

Why I don't like the term "AI"

Content note: I replicate some ableist language in this post for the sake of calling it out as ableist.

In games research, some people take pains to distinguish artificial intelligence from computational intelligence (Wikipedia summary), with the primary issue being that AI cares more about replicating human behavior, while CI is "human-behavior-inspired" approaches to solving concrete problems. I don't strongly identify with one of these sub-areas more than the other; the extent to which I hold an opinion is mainly that I find the distinction a bit silly, given that the practical effects seem mainly to be that there are two conferences (CIG and AIIDE) that attract the same people, and a journal (TCIAIG - Transactions on Computational Intelligence and Artificial Intelligence in Games) that seems to resolve the problem by replacing instances of "AI" with "CI/AI."

I have a vague, un-citeable memory of hearing another argument from people who dislike the…

Using Twine for Games Research (Part III)

Where we last left off, I described Twine's basic capabilities and illustrated how to use them in Twine 2 by way of a tiny hack-and-slash RPG mechanic. You can play the result, and you should also be able to download that HTML file and use Twine 2's "import file" mechanism to load the editable source code/passage layout.

Notice that, in terms of game design, it's not much more sophisticated than a slot machine: the only interesting decision we've incorporated is for the player to determine when to stop pushing her luck with repeated adventures and go home with the current spoils.

What makes this type of RPG strategy more interesting to me is the sorts of decisions that can have longer-term effects, the ones where you spend an accumulation of resources on one of several things that might have a substantial payoff down the road. In a more character-based setting, this could be something like increasing skill levels or adding personality traits.

Often, the game-…