Why I Write

I did not start writing because someone told me it would make me a better engineer. I started because my head was too full and I had no system to process it.

Late nights in Kathmandu, staring at the ceiling after a long debugging session, I would find myself thinking about things that had nothing to do with code. About family expectations. About what I actually want from life versus what I am supposed to want. About the pressure of building a future while the present keeps slipping away quietly.

Those thoughts had nowhere to go. So they would loop. The same questions, the same confusion, the same weight. Until one night I opened a blank document and just started typing. Not to publish. Not to impress anyone. Just to get the noise out of my head and see what it looked like on a screen.

That was the beginning.

Writing as Thinking

I build backend systems for a living. I think in terms of architecture, data flow, failure modes, and trade-offs. And somewhere along the way I realized that writing does the same thing — but for thoughts instead of requests.

When I write about a technical decision, I find out whether I actually understand it or I was just going along with it. When I write about a life question, I find out whether I have a real position or I am just repeating what I have heard from others. The page does not lie. If the logic is broken, the paragraph falls apart. If the feeling is unclear, the sentence sounds hollow.

Writing is the closest thing I have to a compiler for my own mind.

Beyond Engineering

This space is not an engineering blog. It never was.

Yes, I write about systems design, architecture decisions, project lessons, and debugging stories. But I also write about things that have nothing to do with code:

• Why the pursuit of a better future sometimes ruins the present
• What responsibility actually means when your parents sacrificed everything
• The tension between ambition and peace
• What it feels like to be young in Kathmandu, building something from nothing
• Money, discipline, identity, and the pressure of figuring it all out
• Late-night questions about existence that deserve more than a passing thought

I think about these things constantly. And if I do not write them down, they stay as half-formed feelings that I cannot learn from. Writing turns confusion into something I can look at, challenge, and actually understand.

What Lives in This Space

This is my thinking archive. A second brain that I can revisit when I forget what I concluded at 2 AM three months ago.

Here you will find:

• Engineering deep dives — what I built, how it broke, what I learned
• Philosophy and life questions — purpose, existence, responsibility, inherited beliefs
• Personal reflections — career struggles, growth, decisions, and doubt
• Project lessons — the real story behind the things I ship
• Startup and product thinking — ideas, observations, and honest assessments
• Travel and solo reflections — what changes in your head when you move through unfamiliar places

There is no single theme. The common thread is that I was thinking about something deeply enough to sit down and write about it.

Why I Publish Publicly

Writing privately would still help me think. But publishing does something different.

When I know someone might read this, I hold myself to a higher standard. I cannot leave an argument half-finished. I cannot hand-wave through a feeling I do not fully understand. The possibility of a reader forces me to be honest and precise in a way that private notes never do.

There is also something about putting your thinking out in the open that makes it real. A thought in your head can be anything. A published piece is a commitment. It says: this is what I think, and I am willing to stand behind it.

Some of these pieces might resonate with someone going through the same confusion. Some might not. That is fine. I am not writing to build an audience. I am writing to build clarity, and publishing is the pressure that keeps the clarity honest.

What This Archive Means to Me

I am someone who builds systems during the day and questions everything at night. I balance engineering deadlines with existential confusion. I think about database migrations and the meaning of responsibility in the same week. That is just how my mind works.

This writing space is where both sides meet. It is where the engineer and the thinker sit at the same table. It is where I slow down enough to understand what I actually believe, instead of just reacting to whatever is in front of me.

Every piece here is a snapshot of my thinking at a specific moment. Some of them I might disagree with later. That is the point. Growth looks like a trail of updated conclusions.

If you are here, you are welcome to read whatever catches your attention. No particular order. No curriculum. Just one person trying to make sense of systems, life, responsibility, and himself — one essay at a time.

That is why I write. And that is why this space exists.