When I changed careers into tech, I had a mental retro about what I could've done better in my past career, coming to the conclusion that:
- I didn't stay connected enough to the community and...
- I found situations that were comfortable and held onto them, avoiding opportunities that challenged me.
So, I made a conscious decision to do the opposite of both of those. I looked for leadership and organizing opportunities in the local tech community and identified things that I was scared of doing, and actively sought out chances to do them.
Public speaking topped that list. 😱
Fast-forward to 2019, after sending out CFPs (calls for paper, or talk proposals) here and there for a year, I got my first acceptance to a major conference, RailsConf. 🎉 It was a conference that I had wanted to go to for a couple years, where some of my Coding Heroes will be presenting, as well. Naturally, I was at the same time excited, honored and of course, terrified!
Spoiler alert: I survived.
Since RailsConf in May I have given that same talk two more times, at THAT Conference in WI and RubyConf, getting less and less terrified each time. Some folks (mostly other Code Newbies) have expressed shock that at less than 2 years in tech, I was "already" speaking at conferences. I always told them that they can too, and should.
Here are the reasons why.
We bring a set of new perspective with us when we come into the tech industry. Our experiences before entering tech might inform a simpler approach to completing the task or we might ask different questions than a Senior Engineer would. While our experience might be limited, we are also not weighed down by the same indoctrination and baggage as someone who'd spent decades in the industry. CodeNewbies are inventive. We don't have the notion of "we've always done it this way"; All these tools are new to us and in our attempt to manipulate computers to do complicated things, we sometimes discover new ways to use these tools that folks might not have thought of.
And what better place to share these discoveries than on a conference stage?!
When I first decided to submit a proposal for a conference talk titled "Bridging the Knowledge Gap: Debugging", I was not good at it. Whenever I had to track down a bug, I froze. I had no idea when to use what tool.
Should I put a
binding.prysomewhere? If yes, where?
I always forgot to look for information in error messages or server logs. My pair, if I was pair programming, always had to make suggestions and point out the next steps to me. I constantly wished that my bootcamp had taught me more about debugging.
The purpose of the talk, other than to get into speaking, was to pick a topic that I want to get better at or know more about. This gave me a reason and accountability to do a deep dive that I otherwise might keep putting off. I learned so much during the research phase of preparing the presentation. Now that I've given the talk a few times, I'm feeling more comfortable applying those tools in my daily workflow.
Long before my first trip as a speaker to RailsConf, I've wanted to go as an attendee. I streamed the talks from the main room from afar the two years prior to 2019. I watched videos of presentations by really smart folks like Aaron Patterson, Eileen Uchitelle and Justin Searls. I always learned a lot from their talks and regarded them as "coding celebrities".
Attending conferences, it's pretty much a given that you'll meet new people and create professional connections. Attending as a speaker takes this to a whole new level.
A lot of conferences host a reception or dinner for speakers at some point. The ones that I had been a part of took place the night before the first day. At these events, I was able to meet some of the people I looked up to in the Ruby community. I can say, with 100% truthfulness, that I "had dinner with DHH", the creator of Ruby on Rails. We don't have to talk about the fact that it was in a room of about 100 people.
My favorite interaction with one of the "coding celebrities" mentioned above was when Justin Searls tweeted about being nervous before a talk after 10 years of speaking, I replied that it was a relief to hear him say that as a first-time speaker. Then, he came to my talk and complimented me afterwards! 😮
More than that, I have met folks who inspired and encouraged me to write more (Molly Struve), speak more (Colleen Schnettler), take better care of myself (Avdi Grimm), among others. Many of whom I also now consider friends.
All that said, the best reason I have found for me to keep speaking (even though imposter syndrome runs amok) is this:
There's always someone working to be where you are.
Even though I started speaking as a major stretch goal in a new career and to face my fears of public speaking, I keep doing it because I want to inspire other early-career developers to get up and share their learnings and experiences. Experts shouldn't be the only voices we hear on conference stages. Representation matters and we're already experts of our own experiences.
Now I'm going to shamelessly include a video of my first conference talk:
Articles on writing proposals:
What I learned from reading 429 conference proposals by Noel Rappin
Conference Prompts: Or How to Submit Proposals and Influence People by Noel Rappin
What Your Conference Proposal Is Missing by Sarah Mei
I would also recommend checking out your local Write/Speak/Code meetups. They do a great program called Own Your Expertise that I highly recommend.