I didn’t start coding because I was some prodigy kid dismantling radios at age nine.
I started because curiosity refused to shut up—and because Google kept saying “learn to code” like it was a life hack I hadn’t tried yet.
My first lines of code were ugly.
Not “wabi-sabi” kindly ugly you know?. I mean crime-scene ugly type-shi.
Things broke. Often.
Semicolons went missing like your girlfriends when rally in Naivasha..... I digress😂😂.
Errors stared back at me with zero empathy and full confidence.
But somewhere between debugging at 2 a.m. and celebrating a button that finally worked, something clicked:
Code isn’t magic. It’s communication.~ FKiche 25'
You’re talking to a machine.
You’re also talking to future-you.
And if you’re brave enough—other humans too.
The Silent Struggle of New Devs (Yes, That One)
Early on, I thought real developers didn’t ask questions.
Spoiler: they do. Constantly. Loudly. Yes, be it AI or Stack Overflow, we need answers and we need them now dammit.
I thought documentation was boring.
Another spoiler: bad documentation is boring. Good documentation saves lives. Or at least deadlines.
I’d learn something today, forget it tomorrow, re-learn it next week, and swear I’d “write it down next time.”
Next time never came… until it did.
That’s when technical writing snuck up on me.
Why I Started Writing (Besides Therapy)
I didn’t wake up one day and declare, “I am now a technical writer.”
Nope. I just got tired of re-learning the same things. And Stacy mentioned it severally😂
So I wrote:
Notes that turned into explanations
Now join me in turning these explanations turned into posts
Posts that somehow helped other people
And that feeling?
That moment when someone says “this finally made sense”?
Yeah. That hits different.
The idead of writing forced me to slow down.
To stop pretending I understood something just because the code ran.
If I couldn’t explain it simply, I didn’t understand it deeply. Period.
dev.to Felt Like the Right Place
dev.to doesn’t demand perfection.
It welcomes honesty.
You can show up as:
a beginner
a learner
a developer mid-confusion
a developer mid-breakthrough
That’s powerful.
This platform feels less like a stage and more like a campfire.
We’re all swapping stories about bugs that humbled us and wins that kept us going.
What I’m Writing About (And Why)
I’m not here to act like an expert.
I’m here to document the climb.
Expect posts about:
- - Learning curves that felt vertical
- - Concepts that clicked after frustration
- - Tools that confused me before they empowered me
- - Mistakes I don’t want you to repeat
If it helps one person shave an hour off their debugging time—or feel less alone in the struggle—worth it.
Final Thought (No Sugar, Just Truth)
Coding will humble you.
Writing about coding will humble you faster.
But together?
They sharpen each other.
So here I am—
still learning, still breaking things, still asking “why,”
and now, finally, writing it down.
If you’re starting out too:
you’re not late.
you’re not behind.
you’re right on time.
See you in the comments.
Let’s build. Let’s explain. Let’s get better—out loud. 🚀
Top comments (0)