PyData Carolinas Recap & Presentation Reflection
I was fortunate enough this year to attend the first PyData Carolinas conference, though my attendance was only made possible with the development and delivery of a tutorial talk. My colleague Rob and I proposed and then delivered a 90m tutorial talk on using NetworkX to do Social Network Analysis in Python (repo, video coming soon). The talk was aimed at intermediate users of python with some experience with data and the python language. Preparing the talk was quite the adventure – there are a lot of things to plan for and at the end of the day there’s always something to forget about.
What went well:
- Full house! We had a full and captive audience, which was great for the first tutorial of the conference at 9am.
- Our room host, Ginny, was fantastic! And so was our AV guy Doug!
- People seemed to be interested in the topic – one woman mentioned during the closing statements that she was excited to apply the social network stuff she had learned
- Lots of laughs from the terrible jokes we made
- Interesting follow-up conversations and questions after the talk
Improvement Areas & Future Ideas:
- Since it was a tutorial and not simply a talk, my philosophy was that it was necessary to delve into more of the technical details and code. I think some of the code presented was probably unnecessary or could be added to supplementary materials.
- In the future, I think a good solution may be to build a package specifically for a tutorial. In this package I’d probably hide all the helper functions (basically transforming data structure A to data structure B) in a module to load in and not necessarily cover them in a presentation.
- I thought converting our notebooks to slides was a great way to present high-level and technical detail information. We had some issues with a smaller screen than I expected and some people had a hard time reading the code slides in the back of the room. When viewing slides on NBviewer, the browser zoom doesn’t increase the cell size, so I ended up plowing through the notebooks themselves (which I could zoom in on) rather than the slides.
- Next time I’ve got to think about a better way to present code – perhaps screenshots? There’s still a weird area between putting code in notebooks, not inducing a lot of friction to convert them to slides, having code slides be viewable in a presentation, and allowing a user to execute the code that I’m trying to figure out the sweet spot for.
- Some audience members didn’t get the original link to the repository to execute the code themselves, though we did cover it at the beginning I think we started early or some people were late.
- I think the first slide in future presentations will just be the link to the repo, and I can pass off all the installation instructions to the README there.
- Also, sharing the repo via social media ended up being a big help in getting materials into the audience’s hands. Thankful for our host Ginny to have the foresight to do that! Next time I’ll have to make sure to ask any hosts or conference organizers to use their social media accounts to share materials.
All in all, this was the first conference talk and the longer tutorial-type talk I’ve given, and I think it went really well! We did a lot of things right and got some good ideas talks in general and where to take the tutorial in future iterations.
Ride the Lightning
After staying for the lightning talks on day 2, the conference seemed small and comfortable enough for me to give my own lightning talk on day 3. I decided I would go for it and went home and put together a few slides on all the dumb* things I had been building in my free time and what I had learned from doing them. I was mostly driven by the thought that other people may be building these dumb things but might be intimidated about sharing them. However, the world can use more dumb things, there’s already enough practical* things out there. And sometimes dumb* things turn into big things that are really cool!
Public speaking to me is like running: I don’t feel particularly good at it, but I feel like I should do it anyway. I started running because I was compelled by the research on what running does to improve the brain. Much like I have a body built for sitting and not running, I think I have a brain built for listening rather than presenting. But a lot of people I admire both run and speak, so I figure they must be doing something right and I should emulate those behaviors.
I take a lot of inspiration from BoJack: