How to share what you know (without becoming an influencer)
If youâre anything like me, youâve talked yourself out of posting something useful at least a dozen times this year.
Yes, this year. Itâs January 17th.
You had the thought. You knew it would help someone. And then you convinced yourself it wasnât worth saying because you donât have the audience, the credentials, or the âplatformâ to say it.
This is the biggest lie developers tell themselves.
And itâs costing all of us more than you realize.
I want to share a few ideas about why your voice matters more than you think, why sharing incomplete knowledge is actually the point, and why you donât need anyoneâs permission to contribute.
This isnât about building a personal brand. This is about being useful.
Letâs begin.
I â The next breakthrough might come from you
Hereâs something most people get wrong about innovation: it rarely comes from the center. It comes from the edges.
The person who finally helped me understand Git wasnât a famous educator. It wasnât a viral tweet. It was A successful Git branching model by Vincent Driessen. A random blog post I stumbled onto years ago that made everything click.
Their explanation clicked because of how they said it. Their context. Their specific confusion that matched mine.
React came from a Facebook engineer who got frustrated with how they were building UIs. Ruby on Rails came from a guy building a project management tool. The person who writes the tutorial that changes everything for the next generation of developers might be mass-producing screws in a factory right now. Or teaching third grade. Or nursing a baby during lunch breaks.
Your background is different. Your journey is different. The problems youâve faced are different. The way you think about solutions is different.
That difference is not a limitation. That difference is the contribution.
I learned to code through freeCodeCamp in 2016. I was in my 30s, learning during lunch breaks while my kid napped. No computer science degree. No tech background. Career changer. Immigrant. None of the ârightâ credentials.
For years I thought that disqualified me from sharing what I was learning.
I was wrong.
The biggest ideas often come from people who werenât supposed to be in the room. People who saw the problem differently because they came from somewhere else. People who asked the âdumbâ questions that turned out to be the right questions.
Youâre not competing with the experts. Youâre filling a gap they literally cannot fill. And sometimes that gap is where the next big thing lives.
II â Sharing incomplete knowledge is the point
Hereâs where it gets counterintuitive.
You donât need to wait until youâve mastered something to share it. In fact, waiting might be the worst thing you can do.
When you share what youâre learning while youâre still learning it, two things happen.
First, you help people who are one step behind you. They donât need an expert. They need someone who just figured it out. Someone who remembers what it felt like to not understand. Someone who can explain it in words that make sense to a beginner because they were a beginner five minutes ago.
The curse of knowledge is real. Once you become an expert, you forget what it was like to not know. You skip steps. You assume context. The best explanations often come from people still close enough to the confusion to remember exactly where they got stuck.
Second, you refine your own understanding. Writing forces precision. Explaining something reveals whether you actually get it. The gaps in your knowledge become obvious the moment you try to teach â just ask any DevRel person.
I canât tell you how many times I thought I understood something until I tried to write it down. You start typing and suddenly realize you canât actually explain why it works. So you dig deeper. You read more. You test your assumptions. And when you finally publish, you understand it three times better than when you started.
Teaching is learning twice.
Danny Adams was tired of looking up the same Git commands. So he made a one-page cheat sheet. Posted it on DEV.to. Itâs now one of the most bookmarked Git resources on the platform. He sells the PDF on Gumroad. Thatâs the whole story.
He didnât wait until he was a Git expert. He made something that solved his own problem and shared it.
Two developers in Germany thought Git was hard to learn. So they made Oh My Git!, an open-source game with playing cards and real-time visualization. Got funded. 44 levels. Thousands of downloads. They werenât mass-market game designers. They were developers who wanted the next person to have an easier time.
Your knowledge doesnât need to be complete to be useful. It just needs to be shared. And the act of sharing will make it better.
III â The influencer industrial complex is not the point
Somewhere along the way, we started believing that sharing knowledge is only worthwhile if it scales.
If it doesnât get engagement, why bother? If it doesnât grow your following, whatâs the point? If you canât monetize it, is it even worth your time?
This is creator economy brain rot.
Some of the most important documentation in open source was written by people who will never have a newsletter, a course, or a sponsor. They wrote it because the next person deserved an easier time than they had.
That impulse is the entire foundation of developer culture. It predates influencers by decades. And it will outlast them.
You donât need a content strategy to be useful. You need a notes app and the willingness to hit publish.
The goal is not to build an audience. The goal is to help one person. Thatâs not a consolation prize. Thatâs the actual point.
IV â You donât need permission
This is the part that matters most.
Nobody is going to tap you on the shoulder and tell you itâs your turn to contribute. No credential will ever feel like enough. No follower count will make the fear go away.
The people who share generously? They felt the same resistance you feel. They just decided to post anyway.
Bravery in sharing isnât about confidence. Itâs about caring more about helping than about looking smart. Itâs about deciding that the person who needs your explanation matters more than the critic who might nitpick it.
Every single contribution you see online started with someone deciding their perspective was worth sharing. Not because they were certain it was right. Because they were willing to find out.
And hereâs what happens when you do: you start a conversation. Someone replies with a correction. Keyboard warriors live for this moment. Someone else adds context. Someone shares a different approach. The knowledge gets better because you were brave enough to put the first draft out there.
Thatâs how open source works. Not one genius handing down perfect code from the mountain. Thousands of people contributing what they can, reviewing each otherâs work, building on what came before.
Your post might be wrong. Someone will correct you. Good. Now the collective knowledge is better than if youâd stayed silent.
V â Individual bravery compounds into collective progress
This is the part people miss.
When you share what you know, youâre not just helping one person. Youâre adding to a body of knowledge that didnât exist before. Youâre creating a resource that can be found, shared, built upon.
One person writes a blog post. Another person links to it. A third person writes a better version. A fourth person makes a video. A fifth person translates it into Spanish. Suddenly thereâs a whole ecosystem of resources that exists because one person decided to go first.
Developer communities donât grow because of a few prolific contributors. They grow because lots of people contribute a little. The person who answers one Discussion. The person who adds one example to the docs. The person who writes one âI figured this outâ post.
Thatâs how knowledge scales. Not through influencers. Through participation.
When you stay silent, youâre not just depriving one person of your insight. Youâre breaking a link in a chain that could have led somewhere none of us can predict.
The tutorial that factory worker writes might inspire a CS student in Lagos who builds the next great developer tool. But only if it gets written. Only if it gets shared.
Collective progress isnât waiting for you to be ready. Itâs waiting for you to contribute.
VI â The real barrier
Hereâs the uncomfortable truth.
The barrier isnât knowledge. Itâs fear.
Youâre not afraid of being wrong. Youâre afraid of being judged. Youâre afraid someone will point out that youâre not qualified. That itâs been said before. That youâre not enough.
Let me save you some anxiety: all of those things might happen. None of them matter.
Iâve been there. Early in my career, I closed a GitHub issue and someone replied asking if theyâd left out anything âa qualified personâ would need. Turns out the next commenter backed me up and told them to fill out the issue template properly. I wasnât wrong. But that âqualified personâ line? That one stuck with me anyway. Being wrong in public is not the end of your credibility. Itâs the beginning of it.
The developers worth learning from arenât the ones who never make mistakes. Theyâre the ones who learn in the open. Who share their confusion. Who update their thinking when they get new information â there is immense power in changing your mind.
Your perspective is yours. Your context is unique. The way you explain something is different from how anyone else would explain it.
That difference is the value.
VII â What this looks like in practice
You donât need a brand. You donât need a niche. You donât need a posting schedule.
You need to do one thing: write down what you learned and put it somewhere someone else can find it.
Thatâs it.
Share the solve. When you fix something that took you more than 30 minutes, write it down. Not a polished tutorial. Just what broke, what you tried, and what worked.
Share the confusion. When something doesnât make sense, say so. âI donât understand why X works this wayâ is a valid post. It starts conversations. It surfaces explanations. It helps other confused people feel less alone.
Share the opinion. When you have a take on a tool, a practice, or a trend, say it. Strong opinions, loosely held, are how ideas get refined.
Share the context. When you read something useful, add your perspective. Your annotation makes it more valuable than the original for the right reader.
You donât have to do all of these. Pick one. Do it once. See what happens.
VIII â This is how things change
Every tool you love using started with someone sharing something incomplete.
Every framework. Every library. Every tutorial that helped you get unstuck. Someone put it out there before it was ready. Before they felt qualified. Before anyone asked them to.
Thatâs how knowledge spreads. Thatâs how communities grow. Thatâs how things get better.
Not from the top down. From everywhere at once. From people who decided their voice mattered even when no one was asking for it.
Sometimes the most meaningful change comes from the simplest act: one person speaking up.
You have something worth saying. Youâve learned things that would help other people. You have a perspective that is genuinely yours.
The question isnât whether youâre qualified.
The question is whether youâre willing.
You donât need anyoneâs permission to be useful.
Say what you need to say.
With gratitude,
Andrea