Learning in Public: Why Sharing Your Progress Helps You Grow

Learning in public is the practice of sharing what you’re learning as you learn it — through blog posts, tweets, GitHub repos, or videos. It feels uncomfortable at first. You’re not an expert. You might be wrong. People might judge you. But the benefits far outweigh the discomfort.

Why It Works

When you write about what you learned, you consolidate it. The act of explaining forces you to understand it more deeply than passive consumption. This is well-documented in learning science — teaching is one of the most effective ways to learn.

Publicly, it creates a searchable record of your thinking. Six months from now, someone with the exact same question you had will find your post. That’s value you created from something you needed to do anyway.

What to Share

You don’t need to be an expert. Document what you learned today:

• “I figured out why Python’s sort() and sorted() behave differently”
• “I spent 3 hours on this bug — here’s what it was and how I fixed it”
• “Here’s the project I built this week and what I learned building it”
• “I didn’t understand async/await — here’s the explanation that finally made it click for me”

Your target audience is you-from-six-months-ago. That’s a real person with real questions.

Where to Share

• A personal blog — most permanent, most control
• Dev.to or Hashnode — built-in developer audience
• GitHub — your commit history and README files are public learning logs
• LinkedIn — reaches professional network, good for career visibility

You don’t need to be on all platforms. Pick one and be consistent.

Overcoming the Fear of Judgment

The fear of being wrong publicly is real. Two things help: First, label your posts honestly (“Here’s what I understand so far”). Second, remember that being corrected publicly is a gift — you learn faster, and the correction helps others too.

The developer community is, on balance, kind to people who are genuinely trying to learn.

Conclusion

Learning in public is a compounding investment. Each post is small. Over time, you build a body of work that demonstrates consistent learning, attracts opportunities, and reinforces your own knowledge. Start with one post this week.

Read next: How to Stay Consistent When Learning to Code

External resource: Swyx — Learn in Public