You see a lot of advice around blogging as a developer.
Build your personal brand.
Grow an audience.
Share knowledge.
That’s not why I started.
The real reason
I didn’t start blogging because I forget things.
Actually, I don’t.
But that’s not the point.
What I do want is a clear view of my own roadmap, what I learned, when I learned it, and how I was thinking at that moment.
Not just final solutions.
But:
- the confusion
- the decisions
- the small realizations
- the progress over time
That’s the part you lose if you don’t write things down.
The question people asked me
When I started posting, some friends asked me:
“Why are you even writing blogs? Are you trying to impress someone?”
And honestly, I get it.
From the outside, it can look like that.
But no.
I’m not trying to impress anyone.
What blogging actually is for me
For me, blogging is simple.
It’s a way to:
- track my progress
- document how my thinking evolves
- keep a record of what I’m building and learning
It’s basically a timeline of my developer journey.
Something I can revisit later and understand:
- where I was
- what I struggled with
- what eventually clicked
Why this matters
As developers, we move fast.
We jump between:
- tools
- frameworks
- problems
- ideas
Even if you don’t forget things, you lose context.
You forget:
- why you chose a specific approach
- what confused you at the time
- what changed your understanding
That context is valuable.
And that’s exactly what I want to keep.
Where this will help
Right now, I’m just getting started.
But I already know this will matter when I document things like:
- my homelab setup
- infrastructure experiments
- my shift from frontend (Vue) into Rust and systems
Because later, I won’t just care about what I did.
I’ll care about how I got there.
Finally
So no, I’m not blogging to teach.
I’m blogging to track my own journey.
To see how I evolve over time.
If someone finds it useful along the way, that’s just a bonus.
Top comments (0)