"Everything good, everything magical happens between the months of June and August."
When Jenny Han wrote these words, I doubt she had the open source community in mind. Yet, for our group of dispersed nomads, the summer brings a wave of conferences that allow us to connect in person.
From OSCON in Portland to Drupal GovCon in Bethesda, and Open Source Summit North America in San Diego, there’s no shortage of ways to match faces with Twitter avatars. After months of working on open source projects via Slack and Google Hangouts, the face time that these summer conferences offer is invaluable.
The knowledge attendees gain at open source conferences serves as the spark for new contributions. And speaking from experience, the best way to gain value from these conferences is for you to speak at them.
But, does the thought of speaking give you chills? Hear me out before closing your browser.
Last August, I arrived at the Vancouver Convention Centre to give a lightning talk and speak on a panel at Open Source Summit North America 2018. It’s no exaggeration to say that this conference—and applying to speak at it—transformed my career. Nine months later, I’ve:
- Become a Community Moderator for Opensource.com
- Spoken at two additional open source conferences (All Things Open and DrupalCon North America)
- Made my first GitHub pull request
- Taken "Intro to Python" and written my first lines of code in React
- Taken the first steps towards writing a book proposal
I don’t discount how much time, effort, and money are involved in conference speaking. Regardless, I can say with certainty that nothing else has grown my career so drastically. In the process, I met strangers who quickly became friends and unofficial mentors. Their feedback, advice, and connections have helped me grow in ways that I hadn’t envisioned this time last year.
Had I not boarded that flight to Canada, I would not be where I am today.
So, have I convinced you to take the first step? It’s easier than you think. If you want to apply to speak at an open source conference but are stuck on what to discuss, ask yourself this question: What do I want to learn?
Here’s what you do need: A willingness to do the work of teaching yourself these topics. And like any self-directed task, you’ll be most willing to do this work if you're invested in the subject.
As summer conference season draws closer, soak up all the knowledge you can. Then, ask yourself what you want to learn more about, and apply to speak about those subjects at fall/winter open source events.
After all, one of the most effective ways to learn is by teaching a topic to someone else. So, what will the open source community learn from you?