Why I'm Starting durlabh.dev

Why I’m Starting durlabh.dev

I’ve thought about starting a blog for years.

Like most people in tech, I’ve had plenty of notes, half-written drafts, saved links, random experiments and things I was convinced I would “come back to later.”

Usually, I didn’t.

So I finally built this.

durlabh.dev is basically going to be a record of the things I try, learn, build and occasionally break.

That’s really the whole idea.

Mostly, I just like exploring technology

A lot of what I learn starts with curiosity.

I’ll come across a programming language I haven’t used before and want to understand what makes it interesting. Or I’ll hear people talk about a framework, database, AI tool or architecture and wonder whether it’s actually good, or just popular.

I’m especially interested in the trade-offs.

Not just how do I use this?, but:

• Why was it built this way?
• What is it really good at?
• What gets annoying once you use it seriously?
• Where does it make sense?
• Where does it absolutely not?

That’s the kind of stuff I want to write about here.

There will definitely be AI. I’m spending a lot of time learning and experimenting with it right now.

But this won’t be an AI-only blog.

I still enjoy programming languages, backend systems, architecture, infrastructure, developer tools and the occasional technical rabbit hole that has no useful outcome whatsoever.

Those usually turn out to be the most fun anyway.

I also want to leave myself a trail

This is probably the more personal reason.

You learn a lot over a career, but you forget a surprising amount of it.

You remember that you explored something. You remember roughly what you thought about it. But the details disappear.

I don’t want all of that to just vanish.

Maybe five or ten years from now, I’ll come back here and find things I had completely forgotten about.

Maybe I’ll read an old post and realise I was terribly wrong.

That would actually be pretty interesting.

At least there will be a record that I tried things, changed my mind, learnt something, and kept going.

I like the idea of having that.

And I want to get better at writing

This blog is also practice.

Technical people spend a lot of time learning how to build things, but not nearly enough time learning how to explain them.

And writing exposes weak understanding very quickly.

Something can feel perfectly clear in your head until you try to put it into a paragraph.

Then suddenly it isn’t so clear.

So I’m hoping this forces me to think better, explain things better, and become better at articulating technical ideas.

Some posts will probably be rough.

That’s fine.

I’d rather write imperfectly than spend another few years planning to start writing.

That’s pretty much it

No grand content strategy.

No promise of publishing every week.

No attempt to turn every experiment into a “10 things I learned” article.

I just want a place where I can write about the things I’m genuinely curious about.

If people find something useful here, even better.

But even if they don’t, I think this will still be worth doing.

For the learning.

For the writing.

For future me.

And mostly, for the love of the game.