Dev Productivity & Tools
Learning in public
Sharing your learning process — notes, mistakes, open questions — helps you remember and can help others. Short post on benefits and how to start.
2026-03-102 min read
"Learning in public" means learning by sharing — writing down what you're learning, your mistakes, and open questions — on a blog, Twitter, or a repo. This short post outlines a few benefits and a simple way to start.
Why share while learning?
When you write or say what you just learned, your brain has to reorganize the information — you remember it longer. When you share publicly, you have stronger motivation to finish (not just notes for yourself) and a chance to get feedback: someone corrects you, suggests sources, or asks questions that push you deeper. You can also help others who hit the same problem.
You don't need to be "good enough" to share
Many people hesitate: "I'm not expert enough to write about this." In practice, learners who write things down often make better reading for other beginners — because you still remember the feeling of "not getting it" and know where people stumble. Sharing "I finally understood X thanks to Y" or "I used to get Z wrong" has value: it's honest and useful for anyone at a similar stage.
Simple ways to start
- Public notes: Instead of only keeping notes in private files, post to a blog or GitHub (e.g. a "learning-notes" repo). A few short paragraphs after each learning session is enough.
- Ask in public: "I'm wondering about X, I tried Y but it's still unclear" — you often get suggestions or pointers from the community.
- Share mistakes: "Last time I did A and hit B; now I do C" — helps others avoid the same pitfall and helps you internalize the lesson.
Learning in public doesn't require being an "expert" — just being honest and useful to yourself and others who are learning too.
