Engineer by trade,curious by nature.

01

Early curiosity

I grew up taking things apart — not always being able to put them back together. The same instinct: something is doing something, and I want to know how. Computers were the first thing that gave complete answers.

02

Discovering programming

In college I found competitive programming through a club, wrote my first C++ solution, and immediately understood: this is the medium. The feedback loop of writing something and watching it work — or failing, and having to think harder — was addictive in the best way.

03

First real project

The jump from competitive programming to production code happened when I joined Fonix as a backend intern. Suddenly the constraints were different — not just correctness, but performance, maintainability, and the humans reading my schema next year.

04

The learning mindset

Running the DSA programme at Coder's Cafe taught me that teaching is the best way to learn. You can't paper over your own gaps when you're trying to explain something to someone stuck at exactly the point where your understanding got fuzzy.

Distributed systems

I read about consistency models and consensus algorithms for fun. The CAP theorem is still beautiful.

Competitive programming

Codeforces div rounds, LeetCode contests — the discipline of writing correct code under time pressure.

Open-source tooling

Following the ecosystem around Postgres, Redis, and Node.js internals. Occasionally submitting issues.

History of computing

How we got here: the Unix philosophy, the relational model, the origins of the C language.