Writing3 min read
A Nepali essay blog, a million readers, and an accidental career
I did not start with a CS degree. I started with a Blogspot site writing essays in Nepali — and it taught me more about shipping than any course did.
seowritingcareer
My engineering career started with a Blogspot subdomain and essays written in Nepali.
Not a bootcamp, not a degree — those came later. Just a teenager noticing that students kept searching for Nepali essays and finding almost nothing decent, and deciding to write them.
That blog crossed a million readers. I want to explain why that mattered more to me than the number suggests, because the lesson had almost nothing to do with writing.
Nobody was competing for a language nobody was serving
There was a real gap. Plenty of English essay resources, near-nothing in Nepali. Students needed it and the search results were thin.
That is a boring insight in hindsight, and it is the whole thing. I did not outrank anyone with clever tactics. I wrote the resource that should have existed for an audience being ignored, in the language they were searching in. Underserved languages are one of the last places on the internet where being useful is still enough.
SEO stopped feeling like a dark art
Ranking that blog was my first taste of a feedback loop I could actually reason about. Write a thing. Structure it so a machine can tell what it is about. Wait. Watch the numbers.
I learned what a title tag does before I learned what a div was. I learned
that headings are a structure, not a font size. I learned that internal links
are how you tell a crawler what matters. Years later, when I was implementing
JSON-LD and dynamic sitemaps on production Next.js sites, none of it felt like a
new discipline — it was the same instinct with better tools.
There is an irony in having learned technical SEO before learning to code. It turned out to be a better order than the reverse.
A number on a dashboard changes what you believe you can do
The part I did not expect: watching real people arrive.
Writing into a void is an act of faith. Writing into an analytics chart is something else entirely. Once I had proof that a thing I made from nothing had reached people who never asked for it, the question stopped being could I build something and became what should I build next.
That is the actual origin story. Not the blog — the loop. Make something, put it where people are, find out if it was any good. I have been repeating it since, with progressively harder things: the MERN stack, then cryptography and end-to-end encryption, then Electron desktop architecture, then real-time systems.
The domain keeps changing. The loop has not.
What I would tell someone with no credentials
Ship something small and public, in a niche you actually understand, and let the numbers tell you the truth.
Not for a portfolio — although it becomes one. Do it because it is the fastest way to find out whether you like building things, and because "I made a thing and people used it" is an argument that survives not having the right degree.
I still cannot fully explain the jump from writing Nepali essays to implementing AES-256-GCM in a desktop authenticator. But I know where it started, and it was not in a classroom.