Hello World: Why I'm Finally Writing

After 8 years of building in the shadows, I’m finally shipping publicly and putting my thoughts and experiences along the way into words. Sure, I’ve written some of them down in random places, like a notebook or a Word doc, and probably even notes (which I’ll probably never find again), but never like this—public-facing, where anyone can stumble upon it and read it.

Who I am

If you’re new here and this is the first time you’re meeting me, hi! My name is Naveed (you can call me Ned), a self-taught developer from the Maldives—yes, that Maldives. I love programming, computers and everything technology. I love making computers do things. It gives me great joy when I imagine someone using a feature that I built, and I can look at it and say, “I did that. I made it work.” Yes, I’m a full-on nerd.

What do I mean by building in the shadows? Well, I won’t go too much into detail here—you can see what I’m building on my portfolio—but I’ve been programming since 2017. A decent chunk of my earlier projects never made it to GitHub because I never really thought about version control or any of that until mid-2018. The ones that were? I’ve deleted or archived most of it. Most of my projects were private repos anyway. And most of the stuff I built was for personal use or for friends. That is what I mean by “finally shipping in public.”

In late 2025, I began on one of my most ambitious projects yet. Kronos. A human-readable programming language, initially built in Python with similar syntax, and later ported to and continued in C. I’ll be creating a separate blog post about that later.

Why now?

Well, the question I had, and maybe you might be having, is, why now, and why me? Let me answer that first one.

I remember the old days, before AI, when I’d spend hours debugging issues with whatever project I was working on, reading Stack Overflow posts, looking at GitHub issues, comments, and docs… reading blog posts, Medium posts, etc. That was a time in my life when I spent a lot of time doing research. Researching on how I can do a specific thing, how I can fix a specific bug, or do something more efficiently or differently.

And I hope that someday, my blog posts —the journey I’ve been on, the lessons I’ve learned —will help someone the way the people who indirectly helped me did—inspiring and supporting the next generation of programmers, even if AI is coming for all our jobs.

Why me?

Honestly? I don’t know. I’m no one. I’m not gonna claim to be an expert, I’m not. If you think I am, I’m sorry, but you’ve been misled. I myself am learning about new technologies every single day, realising that what I learnt yesterday is now irrelevant. Technology and the web are changing, and it’s changing at a pace far greater than anyone has ever seen before, because of AI. Whether that is good or bad remains to be seen.

What to expect

Enough about AI taking over the world, let’s talk about what you can expect from my blog posts. I’m not guaranteeing anything, and I will be talking about the things that excite me about tech. This can be technical deep dives into the things I’m building, such as Kronos, ForgeKit (a CLI tool for wrangling PDFs, images, audio, etc…) or any other rabbit holes I fall into next, learning in public, sharing my mistakes, things I’ve learnt, how I came about fixing those mistakes and everything in between.

I will make no promises on a posting schedule and definitely no newsletter (yet). Just me, writing code, and the occasional hair-pulling with difficult bugs, and the thoughts I have during that, put on here for the world to read.

-Ned