How I got here, the long version

I'm a middle school student, and I got into building the backwards way. Most people learn the fundamentals first and build later. I did the opposite, and I don't think I'd change it.

I started by vibecoding on tools like Base44 and Lovable. I could describe what I wanted and get something on screen, which was addictive, but I didn't actually understand what was happening underneath. So I made myself slow down and hand-write plain HTML and CSS until the magic turned into something I could reason about. That gap between making something work and knowing why it works is the thing I keep chasing.

From there I moved into full-stack work, mostly with agent-driven tools like Codex and Claude Code. That changed how much one person can build. A lot of the projects on this site exist because I could go from an annoyance to a working tool in an afternoon instead of a month.

Almost everything I've made started as something I wanted for myself. Fracture Studio came out of debate. ClaudeKeeper came out of a laptop that kept falling asleep mid-run. Unslopify came out of watching agents write the same filler over and over. I build because something in front of me is broken or slow, and fixing it myself is faster and more satisfying than waiting.

Not everything worked. Plenty of my early projects broke, got abandoned, or turned out to be things nobody actually needed, including me. But every one of them taught me something the next one used, and that trade felt fair. I'd rather ship ten rough things and learn than plan one perfect thing forever.

Away from the screen I'm into hardware, cricket, and quiz bowl. Different surfaces, same instinct: take something apart, figure out how it works, and come out a little sharper.