Learn In Public Without Waiting Until You Feel Like An Expert

Comparing LinkedIn comments, original posts, X threads and newsletters for learning in public, the comment wins for anyone not ready to teach: it needs no audience and no finished opinion to defend. Posts, threads and newsletters all ask for more confidence than most people have on day one, which is why so many drafts die before publishing.

What does learning in public mean?

Learning in public means posting your unfinished thinking where other people can see it, instead of waiting until you have a polished conclusion. The developer Shawn “swyx” Wang popularized the phrase in a June 2018 essay arguing that writing down what you are learning, before you are any good at it, teaches faster than studying alone (swyx, “Learn In Public”). It does not require a following. About a quarter of US adults already use LinkedIn, and most use at least YouTube or Facebook, according to Pew Research Center’s June 2025 tracking, so the audience infrastructure already exists without building anything new (Pew Research Center, Social Media Fact Sheet). The habit spans more than one platform: developers use GitHub’s own build-in-public topic page to track projects shared while still unfinished (GitHub, build-in-public), and communities like Indie Hackers exist specifically around founders narrating unfinished projects.

The verdict: start with a comment

The smallest version that works is a comment on someone else’s post: a reply that names the specific thing you are still confused about, not a compliment. It needs no audience and no finished opinion to defend, which is why it beats a LinkedIn post, an X thread or a newsletter for anyone who has not taught anything yet. Once a few comments draw good replies, a short original post is the next size up, then a thread, then a newsletter. Each step asks for more confidence than the one before it. Skipping straight to a newsletter is usually why people quit after one issue.

Why does a comment feel safer?

A comment feels safer because someone else already opened the page. They set the topic and took the risk of posting first. All you add is one specific, honest reaction to a part you did not understand or a claim you would push back on. That is a much smaller ask than deciding what your first solo post should even be about. Advice on building a new professional skill often points toward small, frequent practice over big infrequent efforts, a theme that recurs across Harvard Business Review’s ongoing archive of career-development writing (HBR, Managing Yourself). Whether regular AI use is itself reshaping people’s thinking skills was the cover story of the American Psychological Association’s own magazine in 2026, which is one more reason to practice an underused skill like public writing deliberately rather than assume it develops on its own (APA, Monitor on Psychology).

When should you post your own take?

Post your own take once a few comments have drawn specific replies, not just likes, because that is the sign you have something worth saying on your own page. A short post is one paragraph: what you tried and what you would do differently, with no conclusion or call to action required. LinkedIn’s own blog, aimed at its members, regularly publishes guidance on what to post and how often, a vendor’s framing of what performs well in its feed (LinkedIn, Official Blog). LinkedIn’s talent-focused blog, aimed at recruiters and hiring teams, covers skills-based hiring and how AI is reshaping recruiting, both relevant to how a pattern of public learning gets read during a hiring process (LinkedIn Talent Blog). If the post is about how you use AI at work, tie it to one concrete task rather than a general opinion about AI, which is also what a skeptical manager wants to hear, covered in how to explain AI-assisted work to a boss who doesn’t trust it.

Is a thread worth the extra effort?

A thread is worth the extra effort once you have a problem with steps, not just an opinion, because a thread’s whole structure is sequence, one step leading into the next. X is built around a hook post followed by one idea per reply, a format the platform covers in its own creator resources (X, Official Blog). The tradeoff against a LinkedIn post is genuine: threads take longer to structure, and in my own use, X’s career and work conversation skews more toward tech and startups than LinkedIn’s broader professional base does. Use a thread when you are walking through how you solved something, like reading a confusing tool output or fixing a mistake, not when you are sharing a single realization.

Four formats ranked by risk

Ranked from least exposed to most, based on how permanently your name and reasoning get attached to what you posted:

1. Comment. Attached to someone else’s post, buried in the replies, easy to delete without anyone noticing.
2. Short post. Lives on your own profile, but short enough that a wrong take reads as a passing thought rather than a fixed stance.
3. Thread. Structured and built to be shared, so a mistake in one step can travel further than you intended before you catch it.
4. Newsletter. Sent directly to inboxes with your name in the subject line, the hardest of the four to walk back.

When does a newsletter pay off?

A newsletter pays off once you have four or five rounds of public writing behind you and want one place that shows the arc, not scattered posts across platforms. Substack and similar tools exist specifically to turn that scattered writing into an archive a reader can subscribe to and a recruiter can scroll through later, by the product’s own description (Substack, About). Microsoft’s WorkLab research has tracked how employers evaluate AI use at work in its annual Work Trend Index reports, based on the company’s own published data, part of why a visible archive of what you have learned now carries more weight than a claimed skill on a resume (Microsoft WorkLab, Work Trend Index). The cost is that a newsletter with zero subscribers gets read by almost no one on day one, so the first several issues have to be worth writing for their own sake.

What if I get something wrong?

Getting something wrong in public is normal, and it is often the fastest feedback you will get on an idea. A comment or short post with an unfinished, slightly wrong idea usually draws a correction from someone who knows more, faster than a course or a book would give you at the same depth. If a reply shows you were off, the response is a short follow-up covering what you got wrong and what you think now, no deletion needed. Treat a wrong answer the way you would treat a lazy first draft from an AI tool: worth fixing with one more specific line rather than discarding, an approach covered in fix lazy AI answers with three lines added to every prompt. Employers assessing a candidate’s AI fluency in interviews increasingly look for this kind of visible correction rather than a flawless first answer, a pattern covered in what to say when an interviewer asks how you use AI. Buffer, a social scheduling tool, publishes its own library of guidance on posting frequency and timing as a lever for audience growth, a vendor’s pitch worth weighing against your own bandwidth (Buffer, Library).

You are helping me write one short, honest comment on a LinkedIn or X post about a topic I am still learning. Here is the original post: [paste the post text]. Here is the specific thing I am confused about or disagree with: [describe it in your own words]. Write a 2 to 4 sentence comment that names the confusion or disagreement plainly, avoids sounding like I have it all figured out, and does not just compliment the poster. Do not add hashtags or emojis. Before you write it, ask me one clarifying question if my confusion isn't specific enough to respond to yet.

Act as an editor helping me turn a comment I already left into a short original post for LinkedIn. Here is my original comment: [paste it]. Here is what happened after I posted it, if anything, such as replies or corrections: [describe]. Write a one-paragraph post, under 120 words, that states what I tried, what surprised me, and what I would do differently, without a forced conclusion or call to action. Keep my original wording where it already sounds like me, and flag any sentence that sounds too polished or too much like marketing copy. Ask me first if you need more detail on what I tried.

You are helping me plan an X thread that walks through a problem I solved recently, step by step. Topic: [describe the problem and how you solved it, including any mistakes you made along the way]. Draft a thread of 4 to 6 posts: a hook post that states the problem without giving away the fix, then one post per step showing what I tried and what happened, ending on the fix itself and one thing I would still check next time. Keep each post under 280 characters and flag if any step is too vague to be useful to a reader who has never seen this problem. Ask me clarifying questions about the steps before drafting if the sequence I gave you has gaps.

Act as an editor for a personal newsletter about what I am learning in my field. Here are 4 to 5 short posts or comments I have already published over the past few weeks: [paste them]. Write a single newsletter issue, 300 to 500 words, that explains what I was trying to figure out and how my thinking changed across the posts, then ends with one open question I am still sitting with. Do not smooth over any contradictions between the posts; call them out instead. Ask me what audience is subscribing before you decide how much background to explain.

Act as a recruiter who searches LinkedIn all day. I will paste my current headline, about section, and experience entries. Rewrite the entire profile: a headline under 220 characters that says what I do and who benefits, an about section in first person that opens with the problem I solve, and every experience entry rewritten to lead with outcomes. Use bracketed placeholders for numbers I did not give you. Write plainly; never use words like passionate, results-driven, or dynamic. End with the five search terms a recruiter would type where my new profile should appear, and what to add if I want to rank for them. My profile: [paste it].