In August 1991, a Finnish computer science student posted a short message to an online discussion group. He said he was working on a free operating system as a hobby, that it would not be big or professional, and he asked people what features they would want.
The student was Linus Torvalds. The hobby became Linux.
Today Linux runs most of the world's servers, the phones in billions of pockets through Android, and a huge share of the machines that power the internet. It started as a young person saying, in public, here is what I am trying to build, it is not very good yet, what do you think?
That is what learning out loud looks like at its most extreme. Most of the time it is much smaller. But the mechanism is the same, and it is one of the most underrated tools you have.
What it means
Learning in public is simple to describe. Instead of studying quietly until you feel like an expert, you share what you are learning as you learn it.
You write up notes on the book you just finished. You post the small tool you built this weekend, bugs and all. You explain a concept you only understood yesterday. You show the demo before it is polished. You keep a public record of what you tried, what broke, and what you figured out.
The writer and developer Shawn Wang made the phrase popular in programming circles with an essay simply called "Learn In Public." His advice was to create the learning resources you wish you had found, and to share them as you go, because the act of making them teaches you more than consuming them ever could.
The idea is much older than the internet, though. For centuries, scholars across the Arab and Islamic world taught in open study circles, where students gathered around a teacher, asked questions aloud and argued over texts in front of one another. Learning was something you did with people watching.
Why it makes you learn faster
There is a reason teachers often say they did not really understand a subject until they had to teach it.
When you only read, it is easy to feel like you understand something. The words make sense as they pass by. But the moment you try to explain it in your own words, for someone else, the gaps appear. You reach for the next sentence and find there is nothing there.
Writing in public forces you to go through that test. You cannot hand wave in front of an audience in the same way you can in your own head. Even the thought of someone reading it makes you check your reasoning, look up the thing you were unsure of, and find a clearer example.
So the first person who benefits from your public notes is you.
You do not really know something until you can explain it to a stranger.
Why it makes you learn better
The second benefit is that people correct you.
There is an old joke on the internet, often credited to the programmer Ward Cunningham, that the best way to get a right answer online is not to ask a question but to post a wrong answer. People who would never reply to a polite request for help will rush in to fix a mistake.
That sounds cynical, but it works in your favour. When you share what you think you have learned, people who know more will often tell you where you are wrong. Sometimes kindly, sometimes not. Either way, you just got free feedback from someone ahead of you, on exactly the thing you are trying to learn.
If you study alone, your mistakes can sit inside you for years. If you study in public, they get caught early.
Why it brings the right people to you
The third benefit is the one that changes careers.
When you share your learning consistently, you leave a trail. Anyone can look at it and see how you think, what you have built, how you handle problems and how quickly you are improving. That trail is a far better signal than a CV or a list of courses, because it is real work that anyone can inspect.
Andrej Karpathy is a good example of what this looks like at a high level. Long before he was widely known, he was writing clear blog posts explaining neural networks and sharing code that people could run themselves. Later he released video lectures building language models from scratch, line by line. Thousands of people learned from them. His reputation was built in large part on teaching in the open.
You do not need to be at that level for it to work. Someone who posts a small project every few weeks for two years will be noticed by people who care about that kind of work. Founders find co-founders this way. Engineers find jobs this way. Small businesses find their first customers this way.
A public trail of work is a CV that updates itself.
Why it compounds
Each thing you share on its own is small. A short post, a quick demo, a page of notes. It is easy to think none of it matters.
But public work stacks. Your fifth post is read by people who found your first. Your tenth project is taken more seriously because of the previous nine. Search engines and AI tools begin to surface your work when people ask about your topic. Someone shares an old note of yours with a friend who needed exactly that, and the friend follows you.
Over time, the body of work starts to work for you. Opportunities arrive that you did not apply for, from people you have never met, because something you made a year ago reached them.
This is why it pays to start early, when your work is rough and few people are watching. You get the reps, the habits and the archive before you need them.
The beginner's advantage
The most common objection is: who am I to teach anyone? I am still learning.
That is precisely the point. Experts often struggle to explain things to beginners, because they have forgotten what it felt like not to understand. The small confusions that tripped them up years ago no longer even register.
You, on the other hand, just went through those confusions. You remember which explanation finally made sense and which one did not. That makes you, for a short window, one of the best possible teachers for the person one step behind you.
The trick is to be honest about where you are. You are not claiming to be an authority. You are saying: here is what I learned this week, here is what confused me, here is what helped. That framing is both humble and useful. It invites correction instead of defending against it.
How to start
You do not need a big audience or a polished platform. You need a habit.
- Pick a place. A simple blog, a newsletter, a repository of notes, a social account. Choose one and stay with it long enough to build a trail.
- Share the process, not just the result. What you tried, what failed, what surprised you. Process is often more useful to readers than conclusions.
- Make small things often. A short post every week beats a perfect essay once a year.
- Write for one person. Picture someone a few steps behind you and explain it to them.
- Thank people who correct you. It costs nothing and turns critics into collaborators.
Over time, you will also notice that the people worth knowing in any field tend to recognise each other through their work. A good note gets passed around. A useful tool gets starred and forked. A clear explanation gets quoted. None of that can happen to work that lives only in your private folders.
The fear of looking foolish is real. You will sometimes be wrong in front of others. That is the price, and it is small. The bigger risk is learning in private for years and having nothing anyone can see.
The door you leave open
When you learn out loud, you are leaving a door open. Most people will walk past. A few will look in. Every so often, someone will walk through with exactly the knowledge, offer or friendship you needed.
You cannot predict who that will be. You can only make sure the door is open.
A student once posted that his project would never be big or professional. He was wrong about that. He was right to post it anyway.
Further reading
- Show Your Work! — Austin Kleon
- How to Take Smart Notes — Sönke Ahrens
- The Coding Career Handbook — Shawn Wang



