Substack newsletters. LinkedIn posts. Medium blogs. Or a messy Google Doc no one else will ever see.
If you’re learning something new-coding, design, strategy, systems, writing about it will double the speed and depth of your learning.
It doesn’t have to be public. It doesn’t have to be pretty.
But it has to be real.
Because writing forces you to slow down, organize your thoughts, spot your blind spots, and sharpen your understanding in ways passive consumption never will.
Passive learning ≠ real learning
You can binge a 3-hour YouTube playlist on React.
Scroll 20 well-crafted Twitter threads on business models.
Maybe even highlight a few Medium articles.
And you’ll feel smart afterward.
But until you try to explain the concept in your own words, you won’t know what you actually understand - and what you’ve just memorized.
“If you can’t write it clearly, you don’t understand it deeply.”
Writing is the cheapest, fastest test of comprehension. No grades. No teacher.
Just a blinking cursor asking, “Do you actually get this?”
Ever try explaining something and halfway through…your brain just blanks?
That’s not failure - it’s discovery. It’s your mind running into a gap you didn’t know existed. And once you see it, you can fix it.
Writing makes those invisible gaps visible. It turns “I think I get it” into “I know where I’m lost.”
This is where compounding kicks in
After 10 write-ups on how you built or solved something, you start seeing patterns:
→ The same problems keep showing up
→ Certain assumptions fail every time
→ The same tools quietly carry the weight
Those patterns become systems. And once you have systems, learning stops being a linear grind - it starts compounding.
You don’t have to be a “writer”
Pick a simple rhythm and stick to it:
Mon → “What did I struggle with today?”
Wed → “What finally clicked?”
Fri → “What would I tell someone learning this?”
Keep each entry under 200 words. Don’t over-edit. The goal isn’t to look clever - it’s to think clearly.
The people who learn fastest aren’t the ones with the most raw talent.
They’re the ones who write.
Not for likes. Not for followers. But because writing is how they process, refine, and absorb faster than everyone else around them.
Thinking is messy. Writing makes it real.
Do you write while you’re learning - or only once you feel ready to “share”?

Heart

Knowledge by Execution - Breaking Down Tech for the Mango Man (Aam Aadmi/Regular Person) - https://www.sknexus.org/

SK NEXUS

Writing about what you're learning accelerates comprehension and retention more than passive consumption. The act of explaining concepts in your own words reveals knowledge gaps and forces deeper understanding. Regular writing practice, even in private notes, creates patterns and systems that compound learning over time. A simple routine of documenting struggles, breakthroughs, and explanations can transform how quickly you absorb new information.

The fastest way to learn isn’t reading. It’s writing.

I would generall say, the best way to learn is to do. Stop reading. It’s overrated. Just do, then read for the steps you actually need to continue the doing successfully. :)

nice post!
I would suggest this course I did a while ago
<a href="https://www.coursera.org/learn/learning-how-to-learn" target="_blank" rel="noopener nofollow">https://www.coursera.org/learn/learning-how-to-learn</a>
It teaches you how the brain works and how it learns.
I don’t get paid by this BTW

Exactly! That’s how I learned C++, JavaScript, PHP, Dart, and SQL. When I only read, I’d think, “Oh, that looks simple enough.” But the real learning happened when I started writing—making mistakes, fixing them, and finally understanding the concepts. Sometimes I write in a physical notebook, sometimes in a digital one, sometimes directly in a code editor, and other times I even revise ideas in my head while walking or lying in bed.

I kinda agree, writing boosts a person’s understanding of what he has read/watched.
But I don’t think it is the best. I got the opportunity to mentor younger teenagers than me ( my first internship ) when I was a high schooler and even replace my teacher in teaching my class in the last year of CS major (Android Studio). I really believe that teaching/mentoring is the best and most efficient way to learn, based on two main reasons.
<ol>
<li>
Mentoring/Teaching gives a sense of responsibility: When you read an article with the intention of teaching it, you feel the responsibility and force yourself to understand everything in it, unlike learning for yourself or when working on a project where you can leave small things to learn later (that you’ll totally forget about, tbh). In addition, you need to be able to articulate and explain what you’ve just learned, you can’t pass something off by saying to yourself, “I understand it, but I can’t explain it” (the delusion of understanding).
</li>
<li>
More knowledge of problems/issues people face: When you learn a technology on your own, the best way to really understand it is to build something with it. While building, you’d face some of the bugs people typically encounter. Now imagine this on a larger scale: building 20 projects at once feels like an impossible dream, but helping people solve bugs in those 20 projects is totally doable. This gives mutual benefit, the student learns the technology, and you gain experience solving a huge spectrum of bugs.
</li>
</ol>
Thanks for reading ☺️

Valueable article! Instead reading, doing is powerful when learning bcz it connect your brain with thoughts what you do. When I learn coding or new tech stack, I try to apply that knowledge instead read tons of documentation article pages &amp; it’s practicle for me when I learning