I’ve been building things quietly for a while now, shipping code, debugging at odd hours, figuring things out mostly by myself, and then just… moving on to the next thing without saying a word about any of it, which is something a lot of developers do and nobody really talks about how much you lose when you work that way, because every bug you solve, every concept that finally clicks, every project that taught you three things you didn’t know before, it just disappears into the next task if you don’t stop and write it down somewhere.
That’s the first reason, and if we’re being literal now, it’s less glamorous than me saying “I wanted to share knowledge with the world,” but it’s true: I started writing because I was tired of forgetting things I’d worked hard to understand. And with this happening so often, I think it’s time I started taking action.
But there’s more to it than that
The more I read other people’s technical content the more I noticed something that bothered me, which is that a lot of it is written for a reader who already knows most of what the article is trying to explain, like the writer got halfway through and assumed you’d figure out the rest, or they got so deep into the technical details that the actual point got buried somewhere around paragraph four and never resurfaced, and you’d finish the article feeling like you’d read something without actually learning anything. Trust me, I’ve been in this situation more than you can imagine.
I’ve sat with that frustration enough times that I eventually thought, okay, what would I have wanted to read when I was trying to understand this, and can I just write that instead, because clearly nobody else is going to. So I did.
Writing is where you actually find out what you know
This is the part that surprised me most about writing consistently, because I thought I understood certain things until I tried to explain them, and the moment you try to explain something clearly to someone else is the exact moment you find out where your understanding has gaps, where you’ve been going through the motions without fully knowing why, where you’ve been using something correctly without understanding what it’s actually doing underneath.
Every article I’ve written has sent me back to something I thought I already knew, and I’ve come back with a better understanding every single time, so writing isn’t just something I do after learning, it’s become a core part of how I learn, and that wasn’t something I planned, it just happened.
The tech space needs more honest voices
There’s no shortage of technical content on the internet but there is a shortage of people writing about it like a real human being who has good days and frustrating days and opinions that might be wrong and is willing to say all of that out loud, because most technical writing sits in this very polished, very confident register that doesn’t leave room for “I tried this and it didn’t work for me” or “everyone seems to love this tool and I genuinely don’t understand why” or “this concept took me way longer to grasp than it probably should have and here’s what finally made it click.”
That’s the kind of writing I want to read, so that’s the kind of writing I’m going to put out, covering JavaScript, fullstack development, Python, AI tools, technical writing itself, and whatever is happening in tech that I have something real to say about.
No performing expertise, no writing for the algorithm, just thinking out loud about things I actually care about and hoping it lands with someone who needed to read exactly that.
I write daily across Dev.to, Hashnode and Medium, come find me there.
Top comments (0)