I don't read the manual first. I plug the thing in, see what explodes, and figure out why from the wreckage. That's not recklessness — that's genuinely the fastest way to understand how something works.
CS student by enrollment. Builder, gamer, and chaos engineer by personality. I'm drawn to anything new, anything weird, anything where the rules aren't written yet. If a technology just dropped, there's a good chance I'm already inside it breaking things.
When I'm not writing code I'm deep in a game, going down rabbit holes that probably won't matter but are too interesting to ignore, or exploring tech just because it exists and that's reason enough.
"I don't follow a tutorial. I follow the curiosity."
The best documentation is the error message you get after you've already broken it. That's where actual learning lives, in the debris, figuring out why it went wrong and what to do completely differently next time.
Shivam Tiwari, 2026A full-stack platform built to help students. The tools that existed weren't good enough, so the obvious move was to build one from scratch.
A real-time safety operations platform for Raipur. Built for the city I live in because the problem was real and no one else was building the solution. Live on Vercel.
A full deep dive into PC components, how they actually work, not just what they are. Because understanding the hardware is half of understanding the software.
An app to track your life. Habits, goals, progress, all in one place. Built because no existing app did exactly what was needed.
A friend, literally. Built something that acts as a companion. The kind of project you make when you have an idea that is hard to explain but makes sense once you see it.
The lab never closes. New projects always in progress, some half-baked, some almost done, some just a weird idea too interesting to ignore.
Safety ops platform for Raipur. Civic tech built for the city I actually live in. Running live.
Personal life tracking app. Habits, goals, progress. Built because nothing else fit exactly.
A digital companion project. Hard to explain, makes sense once you see it running.
Plugging AI into places it was not designed to go. Seeing what happens. Ongoing.
Something is always in progress. Check GitHub to see what just got pushed at 2am.
Lives in a notes file. The idea is too good to throw away. Might become real soon.
Every productivity app I tried was missing something. So I built my own. Here's what I learned about tracking your own life in code.
BuildingUnderstanding the hardware changed how I write software. A breakdown of what I actually learned researching every component from scratch.
Hardware + CSService workers, caching strategies, and why offline-first apps are harder than they look. What I figured out building Node Map.
PWA / WebIf you're building something interesting, have a collab in mind, want to break things together, or just want to talk tech and games, I'm around.