The instinct is to learn privately and share once you are competent. Learn in public inverts that: you write up what you figured out today, while you are still visibly a beginner, and you keep doing it.
The obvious objection is that nobody wants to read a beginner's notes. The answer is that beginners do, urgently, because the person one week ahead of you explains things better than the expert who has forgotten what was hard.
Why it works, mechanically
Strip away the community-building argument and there are three effects, all of which apply even if nobody reads a word.
It forces completeness. A private note can say "the auth thing was a token scope issue." A public one has to say which token, which scope, and how you found out, because you cannot rely on shared context you never wrote down. This is a direct defence against the curse of knowledge, which is the reason your own old notes stop making sense.
It forces honesty about what you understand. Writing an explanation for someone else is where vague comprehension collapses. You reach the sentence you cannot write and discover you did not understand the step. That is the Feynman technique with a deadline and a witness.
It creates a searchable record with someone else's vocabulary in mind. Notes written for an audience get titled and phrased in the words a searcher would use, including future you, who has forgotten your private shorthand.
The corrections effect
The social benefit that people underrate: being wrong in public gets you corrected, and corrections are the highest-value feedback available.
Most learning happens with no feedback loop at all. You read something, form a belief, and never find out it was wrong. Publishing a claim invites someone who knows more to tell you, at essentially no cost to you beyond mild embarrassment.
The memory research is unexpectedly encouraging here: errors you made confidently are the ones that correction fixes most durably, an effect covered in the hypercorrection effect. Being confidently wrong in public and then corrected is, from a learning standpoint, close to optimal.
What "public" actually needs to mean
It does not mean building an audience. Ranked by cost, all of these count:
| Version | Effort | What you get |
|---|---|---|
| A note written as if for a stranger | Almost none | Completeness, honesty |
| Sharing in a team channel or group chat | Low | Corrections from people who know your context |
| A personal site or digital garden | Moderate | Searchable record, occasional strangers |
| Regular posts, talks, videos | High | Audience, opportunities, more corrections |
The first row is where most of the benefit lives, and it is available today with no account, no platform, and no risk. Writing for an imagined reader is nearly as effective as writing for a real one, because the mechanism is the writing, not the reading.
The practical shape
Write the thing you needed three hours ago. The best public note is the answer to the question you just spent an afternoon on. Its audience is well defined: people about to spend the same afternoon.
Include the wrong turns. What you tried that failed is more useful than the working solution and is the part everyone omits. It is also what makes a post from a beginner more valuable than one from an expert.
Timestamp and do not retro-edit into false confidence. A note that says "as of March 2026 this is what I believe" ages honestly. Silently updating it to look like you always knew destroys the record of how you learned.
Keep it small. One problem, one note. A comprehensive guide is a project; a note about one confusing thing is fifteen minutes. See atomic notes.
Do not wait to be qualified. The qualification threshold recedes as you approach it, which is the illusion of competence running in reverse: the more you learn, the more you see what you do not know, so you never feel ready.
The honest costs
This is not free, and the enthusiastic version of the advice skips the trade-offs.
Some things should not be public. Anything about your employer's systems, colleagues, customers, or unreleased work. The default at work should be internal, not public, and the line is not always obvious. When in doubt, write it privately.
Public writing invites public criticism, not all of it useful or kind. If that lands hard on you, the team-channel version gets you most of the benefit with far less exposure.
It can become performance. Once there is an audience, the temptation is to write what looks good rather than what you actually learned, at which point the mechanism inverts and you are back to hiding confusion. The tell is when you stop publishing the wrong turns.
It costs time you could spend learning. Roughly true, and mostly false: writing the explanation is the consolidation step, not an addition to it. See why writing helps memory.
Where it sits
Learn in public is the output end of a note system. Capture feeds it, and it feeds back: writing publicly tells you which of your notes were actually complete.
More in writing from your notes, evergreen notes, and personal knowledge management.