// Definition
Learn in Public is an approach coined by Shawn Wang where you share everything you learn as you learn it. Instead of consuming content passively, you create artifacts of your learning: blog posts, tutorials, tweets, videos, talks and put them out in the open.
Forms of learning in public:
- Blog posts / TIL notes - write about what you learned today, even if it feels "too basic"
- Twitter/X threads - summarize a concept you just grasped
- Tutorials - teach others what you just figured out
- Open source contributions - learn by contributing and sharing your PRs
- Conference talks / meetups - present what you recently explored
Key principles:
- Don't wait until you're an expert - beginners writing for beginners create the most helpful content
- Be wrong in public - people will correct you, and that accelerates learning
- Create "exhaust" - every hour of learning should produce some artifact (note, post, repo)
- Own your narrative - your public learning history becomes your portfolio
Learn in Public is NOT about showing off. It's about creating a feedback loop: learn → share → get feedback → learn more.
// Why it might matter to you?
As a developer building a product, you're constantly learning new things: a new API, a pricing strategy, a marketing technique. Learning in public turns that natural process into a marketing engine. Every lesson you share is content. Every mistake you document builds trust. You don't need to be an expert to start, in fact, your "beginner perspective" is exactly what other beginners are searching for. The compounding effect is real: after 6 months of consistent learning in public, you'll have an audience, a portfolio of content, and a reputation, all as a byproduct of learning you'd be doing anyway.
// Related terms
// Want more actionable stuff?
Practical marketing tactics for developers. No theory, just things you can implement.
Join developers who are already reading.