There’s always that one technique. You know, the thing everyone mentions at meetups, the topic that shows up in every tech podcast, the skill that’s supposedly “essential.”
For me, it’s WebRTC.
Ten years building with PHP and JavaScript. I’ve wrestled with async/await until it made sense. WordPress and I have spent enough time together to be on first name terms. I’ve built custom solutions, integrated APIs, made things work when they really didn’t want to.
But WebRTC? Never needed it. Not even once.
And here’s what I’ve learned: that’s completely fine.
We’re not supposed to use everything. The projects you work on shape what you learn.
The problems you solve determine which tools you pick up.
Your path won’t look like mine, and mine won’t look like the person sitting three desks away.
I used to think these gaps were weaknesses. Now I think they’re just proof that you focused on what mattered for your work.
The interesting part? When I mention this, people open up. Suddenly everyone has their own “never touched it” confession. A backend developer who’s never written a React component. A frontend specialist who’s avoided databases. Someone who’s built entire applications without ever setting up CI/CD.
We spend so much energy trying to know everything that we forget: depth beats breadth every single time.
So here’s my question for you.
What’s the popular technique sitting in your blind spot? The thing that’s everywhere in theory but nowhere in your actual work?
Drop it in the comments. I have a feeling we’re all in better company than we think.
Leave a Reply