"I Could Never Speak at Conferences" and Other Things Tech Experts Tell Themselves
When I saw Cory House speak at my first tech conference, I immediately thought, "I could never do that."
He seemed so natural on stage, sharing deep insights about React, cracking jokes, answering complex technical questions without hesitation. Clearly, he was born for this. Right?
Then we had a conversation recently on the Product Driven podcast, and he revealed something that shocked me.
Early in his career, Cory struggled with social anxiety so severe that he was intimidated just walking into a conference lunchroom.
The globally recognized speaker who has presented at hundreds of conferences worldwide, whose Pluralsight courses have reached the #1 spot, and who has built an entire career on his ability to teach and communicate?
He once accidentally sat at the speakers' table because he was too nervous to find a place to sit.
That conversation made me realize how many other developers are sitting on valuable knowledge, unique perspectives, and solutions that could help thousands – but they're held back by thoughts that have nothing to do with their actual capabilities.
The Invisible Wall Between You and Recognition
Software developers often take a strange comfort in being behind the scenes. We convince ourselves that our value is exclusively in what we build, not in our ability to communicate about it.
But what if that belief is just a comfortable excuse?
I know because I've been there.
For years I built things and assumed the work would speak for itself. But here's what I've learned:
Tech expertise without visibility is like building amazing products no one knows about.
As Cory told me, "I was the only developer at a small company. I had nobody to ask. This was when Stack Overflow didn't even exist yet... it was very stressful."
That isolation taught him something crucial: Your knowledge is valuable only to the extent that you share it.
The Myths We Tell Ourselves
Myth #1: "I'm not an expert enough."
Cory didn't start speaking at conferences because he knew everything about React. He started speaking at local, free events about what he'd learned – sometimes just weeks before.
You don't need to be the world's foremost authority. You just need to be a few steps ahead of someone.
As Cory shared, after his accidental speakers' table encounter: "They were kind enough to go, 'Well, why don't you speak about something? I'm sure you have something to teach,' and they encouraged me."
That one moment planted the seed for a career that would eventually take him to 40+ cities a year, speaking to audiences worldwide.
Myth #2: "No one would listen to me."
We assume audiences want perfection. They don't. They want authenticity.
Cory's first Pluralsight course became #1 not because he was the ultimate React authority, but because he genuinely cared about explaining it clearly to people who were where he had been.
As he said, "it was something I wanted to exist in the world. I didn't do it for the money."
When you create content from that place – wanting to make something exist that would have helped you – it resonates in a way that perfectly polished, emotionless content never could.
Myth #3: "I'm too introverted for public speaking."
Introverts often make the best speakers and educators because they think deeply before speaking. They value preparation. They don't waste words.
Cory didn't overcome his anxiety by becoming an extrovert. He built systems around his personality:
"I've just had a rule where I tweet every day... that habit has at least encouraged me to actually write multiple things every day and then share whichever one I think is the best."
Introverts who think they can't speak publicly are confusing personality with skill. Public speaking is a teachable skill, not a personality trait.
Where These Beliefs Comes From
These beliefs don't arise in a vacuum. They're products of:
Comparing our beginnings to others' middles. We see Cory House on stage now, not when he was nervously submitting his first talk.
School systems that rarely taught communication skills to technical people. "From school to the workplace, engineers are rewarded for solving technical puzzles—not human ones."
An industry that often undervalues soft skills. We celebrate technical brilliance but sometimes forget that impact requires influence.
Fear of judgment from peers. Technical communities can be critical places. The idea of putting yourself out there feels risky.
The Hidden Cost of Staying Hidden
When you avoid sharing your knowledge, everyone loses:
Your career moves slower. As Cory demonstrated, his willingness to speak and create content opened doors that coding alone never would have.
Others struggle without your help. Someone is currently fighting with the exact problem you solved months ago.
The industry loses diverse perspectives. If only the naturally confident speak up, we miss countless valuable viewpoints.
You miss growth opportunities. Teaching forces clarity of thought that makes you better at your craft.
Cory revealed that his content creation didn't just build his personal brand – it fundamentally changed how he thought about problems:
"Creating good content helps people see that you're competent. You help them day to day and you hopefully come to mind for them as somebody who they can trust in that field."
Small Steps Toward Visibility
If you're thinking "I could never..." after reading this, here are some baby steps that helped Cory move from anxious developer to recognized authority:
Start with written content. A blog post doesn't require real-time performance. It can be edited, refined, and published when ready.
Find supportive communities. Cory's first speaking opportunity came because someone encouraged him. Seek out groups that lift others up.
Focus on helping, not impressing. Cory's approach is teaching what excited him: "I had these things I wanted to share that I was excited about."
Set small, consistent goals. "I've just had a rule where I tweet every day." Small actions compound.
Pick a specific focus area. Cory didn't try to be an authority on all of JavaScript. He focused specifically on React, which made his content more discoverable and valuable.
The Reality Check
Will everyone become a globally recognized speaker like Cory? Of course not.
But that's not the point.
The point is that your belief – "I could never..." – is probably based on fear, not reality.
And recognizing that distinction changes everything.
Why This Matters for Product-Driven Teams
Product-driven cultures thrive when engineers don't just write code but actively participate in the larger conversation about what they're building and why. When engineers stay silent because "that's not my job" or "I'm just a developer," products suffer.
Product isn't a department—it's a shared responsibility.
The best products come from teams where everyone – including the most technically-focused engineers – feels empowered to share their knowledge, challenge assumptions, and bring their unique perspective to the table.
The Choice That Changes Everything
Cory didn't transform overnight from an anxious developer to a conference keynote speaker. It happened one small step at a time, each one pushing slightly beyond his comfort zone.
His story reminds us that expertise without visibility has limited impact.
You don't need to become a different person. You just need to start sharing what you already know in whatever way feels manageable today.
Because the world needs your perspective – even if your self-limiting beliefs are currently telling you otherwise.
And who knows? Maybe ten years from now, you'll be the one inspiring someone else to think, "If they could do it, maybe I can too."
From Coding to Leading: The Missing Manual
If this article resonated with you, there's more where this came from.
For the past year, I've been pouring everything I've learned about building great engineering teams into a book that tackles the question: "How do we build engineers who don't just write code, but own outcomes?"
Product Driven: The Missing Manual for Engineering Leadership explores how to transform technical teams from order-takers into active problem solvers – the same journey Cory made from anxious developer to recognized authority.
Just like stepping on stage at your first conference, transforming your engineering culture requires overcoming limiting beliefs – not just individually, but as organizations.
The book covers:
How to build focus, clarity, and trust in engineering teams
Why most roadmaps fail (and how to fix them)
The four leadership roles every engineering org needs
How AI is redefining what it means to be an engineer
I'm not asking you to buy anything today. But if you want to be first to know when the book launches (and get access to exclusive pre-release content), join the waitlist.
Join the Product Driven Book Waitlist →
Breaking through your own beliefs is just the beginning. Let's build engineering cultures where everyone can contribute their best thinking.