I grew up curious about how things keep talking to each other.

I was born in a Tier-3 town in Tamil Nadu and grew up in Thanjavur, a Tier-2 city that shaped much of my early life.

I was lucky in one specific way: I had access to technology, and the freedom to explore it. If something caught my attention I wanted to know why it worked, how it worked, and what was happening underneath. Most of that curiosity was fed by endless searching.

It never really left. Even now I'm the kind of person who wakes up in the middle of the night with an idea, opens a laptop, and starts building in a language or framework I've never used — simply to understand it. There's a strange kind of excitement in learning how things work beneath the surface.

After 10th grade I moved to Coimbatore. The move wasn't only about education. It put me among different people, different opportunities and different ways of thinking, and it gave me a wider view of the world than a small town had.

In college I asked the question most students ask: what exactly should I become? I was studying Computer Science with no idea where I belonged. Cybersecurity, application development, networking, embedded systems — everyone seemed to have an answer for me. Some insisted I should focus on Java. I tried. I didn't enjoy it.

So instead of choosing a single path, I explored everything I could get my hands on: reading documentation, watching videos, experimenting with tools, breaking things and fixing them, following whatever sparked.

Then I discovered web development. For the first time I could write a few lines of code and immediately see something come alive on the screen. Build something. Refresh the page. See the result. Repeat. That feedback loop was addictive, and it changed everything.

Around the same time my friend Hari Haran and I spent countless hours learning together — new stacks, side projects, each of us pushing the other to learn more. Those years taught me that learning is far more enjoyable when it's shared with curious people.

What looked like random exploration was revealing something. I wasn't interested in one domain. I was interested in systems — applications, networks, devices, infrastructure, protocols, communities, people. Everything connected to everything else.

That realisation still shapes the way I approach engineering.

In my final year of college I got exactly what I had been hoping for: a startup. Not a large company. Not a corporate office. A startup.

The title was Full-Stack Developer. In reality everyone did a bit of everything, and looking back, that was the best environment I could have asked for.

The founder, Bhagath Singh Karunakaran, had a huge impact on me. Whenever I got comfortable he pushed me to explore further, think bigger, and take ownership of problems that felt slightly beyond my reach. Much of the growth of those years traces back to his willingness to trust me with responsibility before I thought I was ready for it.

The other person who shaped that time was Raja Renga Bashyam, the company's CTO. With more than three decades of building software systems, he became my first real technical mentor, and sitting beside him while he worked through a problem was an education of its own. He didn't teach frameworks. He taught fundamentals — how systems should be designed, how to think before writing code, why simplicity matters, and why understanding the core concepts is worth more than chasing the latest trend.

The startup itself was a crash course in engineering. One day I'd be writing backend code; the next, debugging infrastructure, managing domains and DNS records, testing the application, improving SEO, or sitting in a discussion about where the product should go. There was no clear boundary between development and responsibility.

That environment taught me something I still believe: real engineering is rarely limited to a job title. It's about understanding the entire system and helping wherever the system needs you.

I still build across the layers — from the machines on a factory floor to the web platforms people use every day, and the community in between. Right now that means industrial IoT at i45G, rebuilding a healthcare platform at O2D3, and Kiospal, a community for students, creators and first-generation founders from Tier-2 and Tier-3 towns. What has my attention this month is on the now page; the full record is on work.

What hasn't changed is the fascination: how systems communicate, how ideas become products, and how technology solves meaningful problems when it's built with care.

I don't chase every trend. I prefer fundamentals, long-term thinking, and the technologies that quietly keep the world running. For me, technology has never been only about code. It's about understanding systems — both technical and human.

I don't believe technology is valuable simply because it is sophisticated. Its real value is in what it enables — when knowledge becomes capability, ideas become tangible, and people become stronger because of what we build.

I am still learning — curious enough to question, humble enough to learn, and disciplined enough to turn understanding into something useful.