Writing in Public: How to Learn Faster and Be Found by Opportunities

You know that moment when you finally understand something difficult, and you think: "I wish someone had explained it like this."

That is a good article, waiting to be written. And the person who most needs it is you, six months ago.

Writing in public means sharing what you learn, build and think, through blog posts, notes, threads or short posts, while you're still learning. It's one of the most useful habits you can build for your career, and it doesn't need talent.

Explaining something forces you to find the gaps in your understanding. If you can't write it clearly, you haven't understood it yet. This is closely linked to the study methods in spaced repetition: active recall and teaching beat passive review.

A resume says what you claim. A body of writing and projects shows it. For students and people changing fields, that can matter more than a certificate. It also supports your LinkedIn profile and resume.

People search for answers. A clear post on a narrow topic can reach the exact person who needs it, such as a recruiter, a collaborator or a client.

Readers reply, share and ask questions. Some of the best professional relationships begin with "I read your post on..."

Your notes become a personal knowledge base you can search for years.

You don't have to be. You only need to be a few steps ahead of someone else, or willing to share an honest journey.

Useful posts from non-experts:

• "What I learnt building my first REST API"
• "How I prepared for [exam] in 8 weeks"
• "Three mistakes I made in my first month at work"
• "How I compared two health insurance policies"

Be honest about what you know and don't. Phrases like "here's what worked for me" and "I'm still learning this" are welcome. What isn't welcome is pretending to authority you don't have, or giving advice that could harm people, particularly in money, health and law.

Start from your own life and work:

• Things you just learnt. Explain them simply.
• Problems you solved. Include the error, what you tried and the final fix.
• Projects you built. What, why, how, what went wrong.
• Decisions you made. The options, the trade-offs, the result.
• Mistakes and lessons.
• Summaries of books, talks or courses with your own reflections. See how to read a book so you remember it.
• Answers to questions people ask you. If you've answered the same question three times, write it once.

A simple prompt: "What did I need to know this week that took me more than an hour to find?"

You don't need an elaborate format. Try:

1. A title that says what it helps with. "How I fixed the CORS error in my Express app" beats "Thoughts on web development".
2. The context: who it's for and what problem it solves.
3. The main content in short sections, with examples, code or screenshots.
4. The takeaway: what to remember or do next.
5. Links to sources and related posts.

• Write like you talk, but cleaner. Short sentences, plain words.
• Use concrete examples with real numbers and names, not abstractions.
• Cut the warm-up. Start with the point.
• Use headings and lists to make it easy to scan.
• Read it aloud to catch awkward phrases.
• Edit after a break. Write the first draft quickly, and revise the next day.

If you use AI tools, use them for brainstorming and feedback, and keep the ideas and voice yours. Always check facts. See writing better AI prompts.

You don't have to choose one forever. A common approach is to write a longer post on your own site or one main platform, then share parts of it elsewhere.

"What if I'm wrong?" You might be. Correct it publicly and thank the person who pointed it out. That builds trust.

"What if nobody reads it?" At first, few will. That's fine, because your first audience is yourself. Early posts are practice.

"What if my boss or colleagues see it?" Don't share confidential information about your employer, clients or colleagues. Check your company's social media policy. Write about ideas and your own learning, not internal details.

"Others already wrote about this." Not in your voice, with your examples, for your reader.

"I don't have time." Start with 20 minutes. A weekly short note is enough.

1. Pick a cadence you can keep. One post every one or two weeks is realistic.
2. Keep an ideas list. Add to it whenever you learn something or answer a question.
3. Schedule writing time. Use a short protected block. See deep work and focus.
4. Publish before it feels ready. Done beats perfect.
5. Review every 3 months. See which posts people read or reply to, and write more like them.
6. Be patient. Compounding takes a while. The posts you write now might help someone years later.

• Credit sources and link to them. Don't copy text or images without permission or licence.
• Don't share private data, such as other people's details, documents or conversations, without consent.
• Be careful with advice. If you write about money, health or law, say you aren't a professional, and point to official sources.
• Disclose sponsorships and affiliate links.
• Be kind. Disagree with ideas, not people.

Not at first. Start anywhere you'll write consistently. A personal site is a good long-term home because you control it.

As long as needed and no longer. 400 to 1,500 words is typical. A short, clear post is better than a long, padded one.

The one that reaches the readers you want and in which you write best. Writing in your first language is a strength, and there's an audience for it.

Write useful posts on specific topics, share them where relevant communities gather, reply to others' posts, and be patient. Search traffic builds slowly.

It can, through visibility and proof of skills, but there are no guarantees. It also makes you better at thinking and communicating, which helps wherever you work.

Platform features and policies change. Check the terms of any service you publish on.