You open a blank page. The cursor blinks. You have no idea where to start.
That was me on my very first blog post. I was nervous. I thought, "Who is going to read this? I'm not an expert. I'm just a student."
But I hit publish anyway.
Then I did it again. And again. And again.
101 times later, here I am — looking back at what writing all those posts actually taught me, not just about code, but about people, learning, and what it really means to share knowledge online. 🚀
So if you've been following along, thank you. This one's for you.
The Journey: From 1 Blog to 101
My first post was short. The formatting was rough. The writing was stiff.
But it was honest. And it was mine.
Over time, I started covering topics I genuinely cared about — VS Code updates, CSS history, DNS, React patterns, AI tools, Next.js SEO, and a lot more. I wasn't picking topics to go viral. I was writing about things I was learning, experimenting with, or genuinely curious about.
That turned out to be the best strategy I never planned.
What I Learned From Writing 101 Blogs
1. Consistency Beats Perfection Every Single Time
My early posts weren't perfect. Some of them still aren't. But I kept going.
The moment I stopped waiting to be "ready enough" to write, the writing got better on its own. Showing up regularly — even when the draft feels messy — teaches you more than any writing course ever could.
Lesson: Publish imperfect work. Improve over time. Don't wait.
2. Simple Writing Is Harder Than Technical Writing
Anyone can write a complicated explanation. Writing something a beginner can actually understand? That takes real skill.
I spent more time simplifying my explanations than I spent researching the topic. And every time I found a simpler way to say something, I actually understood the topic better myself.
Lesson: If you can't explain it simply, you don't fully understand it yet. Writing forces that clarity.
3. Developers Are Hungry for Relatable Content
The posts that got the most attention weren't always the most technical.
They were the ones that started with a real situation — a frustrating bug, a confusing concept, a "wait, how does this actually work?" moment. Readers don't just want information. They want to feel like the writer gets them.
Lesson: Start with the human moment. The technical detail comes after.
4. Writing About Something Teaches You More Than Reading About It
Every time I wrote about a topic — whether it was DNS, CSS Flexbox, MCP, or pagination — I understood it at a deeper level than before.
Writing forces you to fill the gaps. You can't fake your way through an explanation. If you don't understand something, it shows. So you go back, research harder, test things, and come back with clarity.
Lesson: Want to truly learn something? Write about it.
5. Your Audience Is More Diverse Than You Think
I assumed my readers were mostly experienced developers.
I was wrong.
Students, career-switchers, beginners, self-taught developers from countries all over the world — they all showed up. That changed how I write. I stopped assuming prior knowledge. I started explaining from the ground up, without being condescending.
Lesson: Write for the beginner in the room. Advanced readers can skim. Beginners can't.
6. The Title Is Half the Battle
I spent maybe 10 minutes on the title of my first blog. I now spend more time on the title than any other single line.
A great title answers: "Why should I click this?" The answer has to be fast, clear, and honest. Clickbait burns trust. Good titles build it.
Lesson: Spend real time on your title. It's a promise to your reader — keep it.
7. Burnout Is Real, and Breaks Are Necessary
Around post 60-something, I hit a wall. Writing felt like a chore. Topics felt recycled. Everything felt dry.
I took a short break. Came back. The energy returned.
Sustainable content creation isn't about writing every single day without rest. It's about protecting your curiosity so it stays alive long enough to keep going.
Lesson: Rest is part of the process. Protect your enthusiasm like it's a resource — because it is.
What I Was Actually Trying to Teach You
Every blog I wrote had the same hidden goal underneath all the headings and code snippets:
Make developers feel less stuck and more capable.
That's it. That's the whole mission.
Whether I was explaining how DNS works or why pnpm is faster, I was always asking myself: Will the person reading this feel smarter and more confident after finishing?
Here's what I hoped you took away from the different posts:
- From the CSS and frontend posts → That styling doesn't have to be a fight. When you understand the model, it clicks.
- From the VS Code update posts → That tools evolve fast, and staying updated doesn't have to be overwhelming if someone breaks it down for you.
- From the AI posts → That AI is a tool, not a threat. Understanding it makes you more useful, not replaceable.
- From the networking and DNS posts → That the internet makes a lot more sense when someone traces through it with you step by step.
- From the personal posts → That every developer — no matter where they are — deals with doubt, confusion, and imposter syndrome. You're not alone.
What I'm Still Learning
I'll be honest: I don't have everything figured out.
I'm still learning how to make my code explanations clearer. I'm still figuring out the right balance between beginner-friendly and technically rigorous. I'm still working on writing introductions that grab attention in the first two sentences.
But that's kind of the point.
101 blogs in, and I'm still learning. That should tell you something — writing is never really "done." It just gets better if you keep going.
Why You Should Start Writing Too
If you've been thinking about starting a blog, here's my honest pitch:
You don't need to be an expert. You need to be one step ahead of someone who's stuck.
That gap — between where you are and where a beginner is — is your entire value as a writer. Use it.
Write about what confused you last week. Explain the thing that took you three hours to figure out in five minutes. That's the blog post someone needs right now.
Conclusion
101 posts. Hundreds of topics. Thousands of words.
But if I had to distill everything into one sentence, it would be this:
The best thing I ever did for my learning was starting to write in public.
It made me a clearer thinker, a better communicator, and a more empathetic developer.
Thank you for reading. Thank you for the reactions, the follows, and the quiet encouragement of just showing up.
Here's to the next 101. 💡
If you want to read more posts like this, head over to hamidrazadev.com — everything is there. If this post helped you or made you smile, share it. And if you're thinking about starting your own blog, drop a comment. I'd genuinely love to hear from you.
Top comments (0)