Learning in Public Is Harder Than It Sounds

“Learn in public” is easy advice to nod along to and surprisingly hard to actually practice, and I don’t think the difficulty gets talked about honestly very often. The pitch is appealing: share what you’re working through, get feedback earlier, build a record of your growth, maybe help someone else stuck on the same problem. All of that is true. None of it prepares you for how it actually feels to post something you’re still uncertain about and leave it there, visible, while you’re still wrong about parts of it.

The gap between the advice and the discomfort

The advice focuses on the upside because the upside is the easy part to argue for. What it usually skips is that learning in public means making your incompetence visible before your competence has caught up to justify it, and that specific ordering is uncomfortable in a way that’s hard to appreciate until you’re the one doing it.

Private learning has a built-in safety net: you can be wrong as many times as you need to be, in whatever order you need to be wrong in, and nobody sees the discarded attempts. Public learning removes that net, or at least makes it much more porous. Every half-formed understanding you share is now a fixed record, potentially visible to people who understand the material better than you currently do, and the anxiety about that isn’t irrational — it’s an accurate read of the actual social cost, which is real and not zero, even if it’s usually smaller than it feels in the moment.

The performance trap

There’s a failure mode that looks like learning in public but isn’t, and I fell into it more than once before noticing: writing as if you already understand something, to avoid the discomfort of visibly not understanding it yet. This produces content that reads confidently and teaches the author very little, because the entire value of learning in public — the part that actually accelerates learning — comes from being honest about the specific point of confusion, not from performing a polished summary of the conclusion once you’ve already reached it.

The tell, for me, is whether I’m more focused on how the writing will be received than on accurately describing where I actually am in understanding something. Those two motivations produce very different sentences. “Here’s a clean explanation of concept X” is performance, even if every word in it is true. “Here’s where I got stuck trying to understand concept X, and here’s my current, probably incomplete, model of why” is the version that’s actually doing the work learning in public is supposed to do — and it’s also the version that feels much riskier to publish, because it doesn’t hide the seams.

Why the seams are the point

I’ve come to think the seams — the visible confusion, the wrong turns, the moment where an earlier post’s understanding turns out to have been incomplete — are not a cost of learning in public that you tolerate for the other benefits. They’re closer to the actual mechanism by which it helps.

Writing down a genuinely uncertain understanding, in public, forces a level of precision that writing privately doesn’t, because you can’t hide behind vague hand-waving when you know someone might ask a clarifying question you can’t answer. That pressure, uncomfortable as it is, is what turns a fuzzy sense of understanding into an actual, checkable claim. Private notes can stay comfortably vague forever, because nothing forces them not to. A public post creates a small, specific incentive to make the vague part concrete, which is often exactly the part that needed to become concrete anyway.

There’s a second effect, which took longer to notice: an old post that turns out to be wrong, later, is not actually a liability. It’s a record of the fact that understanding developed, which is a more honest and more useful thing to have visible than a feed of only-ever-correct conclusions that quietly hides all the intermediate confusion that got you there. I used to think about deleting or heavily editing old posts I’d outgrown. I mostly don’t anymore. The gap between an old post and a current understanding is, itself, informative — to me, if to no one else.

What actually made this easier

None of the discomfort fully goes away, but a few things made it more tolerable.

Lowering the stakes of any individual post helped more than any mindset shift did. Treating each piece of public writing as one snapshot of a specific moment in an ongoing process, rather than a permanent, final statement of what I believe, changed how much any single mistake in it seemed to matter. A wrong claim in a snapshot is expected, even normal. A wrong claim in something framed as a final verdict feels like a much bigger failure, even when the actual content is identical.

Separating the act of writing from the act of checking helped too. I write down where I’m confused first, in the most honest and unpolished form I can manage, before doing any additional research to resolve it. If I research first and then write, the writing quietly turns into a report of the research rather than an honest record of the confusion, and the part that actually helps other people — and helps me, later, by showing my own reasoning process — gets edited out before it ever makes it to the page.

And accepting that some of what gets published will be flatly wrong, not just incomplete, made the whole thing feel less like a performance with a pass/fail grade and more like what it actually is: a running, honest log of a process that includes error as a normal, expected part of it, not a regrettable exception to be minimized.

Where this leaves me

I don’t think learning in public makes anyone learn faster in some automatic, mechanical sense. What it does is make it much harder to fool yourself about how well you understand something, because fooling yourself privately costs nothing and fooling yourself in a way other people might notice costs enough to make you check more carefully before you publish it. That extra friction, uncomfortable as it is to sit inside of, seems to be most of the actual value. Not the audience. Not the feedback, though that helps too. Just the fact that you can no longer get away with vague understanding dressed up as real understanding, because you know, on some level, that someone might ask you to show your work.