Advice for conf speakers:— Tomasz Łakomy (@tlakomy) August 25, 2018
When someone you care for is speaking, sit in the first row. Be there for them. Laugh at their jokes, _actually_ watch the talk (Twitter can wait), make yourself visible for them.
Be the audience you'd like to have, and next time you will have it.
My approach to supporting other speakers is not really about the audience I would like (we're all different!), but more about making two things happen:
- someone being the best they can be
- them getting credit for that
In fact I've been a speaker coach and mentor for a few years and have variously watched rehearsals, suggested where to stand and not stand, walked nervous speakers around outside before their talk, fetched water ... all sorts of things. However this twitter thread (I got a bunch of tweets and the replies are also great) shows that _anyone_ can give great support to any speaker, whether you know them or not. Here are my favourite three things to do to support anyone giving a talk. Continue reading
- What's going well/what are you excited about?
- What's tedious/annoying or actually a problem?
- What could I be doing that I'm not?
Over time I've developed some particular processes that I find helpful when reviewing code. In particular, I often surprise people at how much review I do before I run the code. Sometimes I grab the branch so that I can use my local diff tools, but I don't actually execute code until I've established some basic facts. This post is a little insight into what's happening in this not-running-the-code-yet zone. Continue reading