The long version

It started with an LED

The first thing I ever made a computer do was blink a light on purpose. Arduino, a breadboard, school-age patience. That’s an unremarkable origin story until you notice what it teaches you: the gap between it should work and it works is where all the real engineering lives.

Arduino became Raspberry Pi, Raspberry Pi became ESP32, and somewhere in there the hardware stopped being the interesting part. What held my attention was everything around it — the server it phoned home to, the network it sat on, the service that had to stay up while I slept. I stopped building gadgets and started building systems.

I completed Class XII in Physics, Chemistry and Mathematics at Sri Abhida Junior College, Hyderabad, at 90%, and I’m now reading for a BTech in Computer Science Engineering at Lovely Professional University, Punjab.

Learning by breaking things

At LPU my real curriculum runs alongside the official one. I learn a subject by executing a project in it — penetration-testing exercises, a home cybersecurity lab, Linux hardening workflows, and a long tail of servers I have configured, misconfigured, and configured again.

If you came here looking for evidence rather than adjectives — a capable CSE student, a cybersecurity-focused one, someone who actually ships — the evidence is the project pages, the repositories, and the write-ups where I explain what went wrong. I’d rather be read than believed.

Work

From October 2024 to January 2025 I was a development intern at Pantech Prolabs India Pvt Ltd, contributing to a production codebase, sitting in code reviews, and working inside sprint-based delivery. It was the first time my code had to survive other people’s opinions, which turns out to be the useful part.

Before and alongside that, I took freelance work for local businesses and independent clients from 2021 — websites and apps, but also the unglamorous half: deployment, hosting, DNS, and the maintenance calls afterwards. Shipping for a paying client teaches you the difference between finished and done.

The Linux Foundation, and LFX

I’m a member of the Linux Foundation and an active contributor and maintainer across its projects. Most of that work is invisible by design: reviews, fixes, maintenance, the slow upkeep that keeps a project healthy long after the interesting commits are done.

That work was recognised by LFX, which granted me a travel fund — funded entirely by LFX — to attend the Linux Foundation Open Source Event 2026 in Mumbai, June 16–18. I wrote about what that meant in Linux Foundation, LFX, and a trip to Mumbai I didn’t pay for.

Open source, and why everything is public

I publish code and documentation with a bias toward practical guides and reproducible setups — web projects, infrastructure experiments, IoT builds. A fair bit of it is unfinished, and some of it is archived. I leave it up anyway. The seams are the part other people can learn from, and hiding them would only flatter me.

The full listing lives on the open-source page, with live numbers straight from the GitHub API.

Elsewhere

• GitHub — source, contributions, repositories
• LinkedIn — professional profile
• Twitter / X — short thoughts
• Instagram — the non-technical half
• [email protected] — usually a reply within 24–48 hours

Projects · Reflections · Resume