When I started writing on Dev.to, the idea was simple.
I was learning AI without a clear path. Jumping between courses, restarting often, and constantly feeling behind. I thought — if I’m struggling to find structure, others probably are too. Maybe documenting the mess would help someone.
That was the plan.
What I didn’t expect was how much it would help me.
🤯 Writing Raised The Bar For Learning
Before I started writing, my standard was simple:
Do I understand this enough to use it?
That was enough.
Writing changed that without me realizing it.
When you know you’re going to explain something publicly, “I kind of get it” stops being enough.
You start asking better questions: why this works, why it’s used over something else, what breaks and why.
The embeddings article made this obvious. I thought I understood it before I started writing. Writing it exposed gaps I didn’t know existed. I had to go back, fill them, and come back again.
I’m not learning faster because I write.
I’m learning at a level where I can explain — not just recognize.
📜 Writing As Proof Of Learning
Right now I’m in that difficult middle phase of learning AI — past beginner, not yet building real things with it.
And when you’re there, it’s hard to show someone what you actually know.
Writing articles solves that quietly.
When someone looks at my profile, they don’t just see a skill listed — they see exactly what I’ve been learning, how I think about it, and how well I understand it.
Not because I claimed to know it — but because I explained it in public, where anyone could point out if I was wrong.
That’s a different kind of proof than listing a skill on a resume.
💬 Learning From The Comments
One thing I didn’t expect at all was how much I would learn from comments.
When my structured output article did well, the comments became an extension of the article.
People shared their experiences. Different ways they were using it. Small details that weren’t obvious while learning alone.
I kept reading and thinking:
I didn’t know that.
That’s a good addition.
That's something I should try.
The article didn’t just go out.
It came back with more knowledge than I started with.
📝 Articles As My Own Notes
I also realized something more practical.
Articles became my best notes.
They’re written in my words, in a structure that makes sense to me.
Easy to revisit. Easy to remember.
Better than scattered bookmarks or someone else’s tutorial.
It’s a slightly selfish reason to write publicly — but it’s also the most useful one.
I don’t just write to explain.
I write so I can come back and understand it again.
🧠 Writing As Memory
Writing also helps me remember things clearly.
Through articles, I can share my experiments, lessons, and experiences with others — but they also help me remember those moments much more clearly.
When I go back and read an article, I remember exactly where I was - the confusion, the phase I was in, what it felt like.
Without writing, that would’ve turned into:
“Yeah, that time was hard.”
Now it’s something I can actually revisit.
Writing preserves context, not just information.
⏱️ Discipline Changes The Way You Learn
Writing consistently also introduced something I didn’t expect — discipline.
There’s something about having a fixed day to post every week and a streak to protect that keeps you honest.
You can’t just say you’re learning — you have to actually show up and do it.
Every week.
The writing makes the learning real in a way that private notes never did.
📈 Seeing Growth From The Outside
Another thing writing gave me is perspective.
When you're learning something new, it's hard to see your own progress while you're in the middle of it. Most of your focus is on figuring out what to learn next.
But when I look back at my articles, I can actually see how my thinking changed.
I went from trying to understand the landscape, to learning individual concepts, and eventually seeing how they connect.
That kind of growth is hard to notice when you're inside the process.
Writing made that progress visible.
🎨 A Side Of Writing I Didn’t Expect
I never considered myself particularly creative.
I always appreciated creative things more than I believed I could create them myself. So writing publicly was never something I planned — I started only because the topics were technical. That felt safe enough.
But somewhere along the way it became more than documenting what I learned. I started finding my own way to explain things. My own voice. My own structure.
And then I wrote the WeCoded article — which had nothing technical in it at all.
That's when I realized maybe I am a little creative after all.
🌱 The Realization
I started writing thinking it might help someone else.
It might.
But more than that, it helps me learn better, remember more, and understand things more deeply.
And that's not what I expected when I started.
The audience is a bonus.
The real value is what writing does to the learner.
Top comments (0)