August 18, 2017
I’m writing a blog post series about preparing technical talks, here are the five parts:
Today, I’ll be covering the first part of my process, finding an idea.
Here’s a great primer on why you, reader, have valuable ideas:
What ideas lead to great talks? My strongest talks share the following traits:
I love Vim. Learning this 25-year-old text editor changed my career. I went all-in on Vim three years ago and have translated my passion into organizing the Vim Chicago Meetup. And, I also love React. React is my tool of choice for the frontend.
Like any technical ability, writing React code well in Vim exists on a spectrum ranging from barely-getting-it-done to ninja flow state.
It takes work to build your Vim into the perfect React development environment. Writing React code means that I seek that perfection. What mappings, plugins, and workflow hacks can I use to get there? It’s a subject that I care about, and that’s the most important trait of a good talk.
An idea that’s explored in Speaking.io is that aspirational talks, i.e.– “I want to know about this subject, so I’ll sign up for a talk and learn it by the deadline”– can backfire. I’ve heard this idea referred to as Talk Driven Development, and if it works for you, great.
I have to start with a base of understanding. I need to already be at least at the same level of the average listener. Only then do I have a chance at pushing myself and my listeners beyond that level into unfamiliar ground.
For passion to translate to an interesting talk, I need to have done the work recently. When somebody is speaking about an idea that’s fresh in their mind, the talk is better.
Another benefit of talking about recent completed work is that I’ve had time to recognize the things I could have done better. I can integrate these lessons into the talk.
Talks are entertainment, and with the right passion, familiarity, and freshness, I hope to produce something worth listening to.
The next post in this series covers an important subject, brainstorming.