Field Notes on
the Operator
Everything that doesn't fit on a resume — the origin story, the AI philosophy, and what happens after the laptop closes.
How this started
I build software the way I chase industrial leads — end to end, without waiting for someone to hand me the clean version of the problem. That habit started at my school days, where my interest in technology turned into fun coding weekends, a dream to build big, and a steady stream of personal projects built for the sake of shipping something real rather than just clearing coursework.
I've always preferred real-world software over academic exercises — which is the honest reason there are seventeen personal projects and counting. Some are genuinely useful (a WhatsApp chat converter, a GPS tracker), some are pure creative indulgence (a hand-animated raccoon game), and a few are half-finished experiments I kept anyway because the process taught me something.
Outside the IDE, I am a gamer who used to love playing games and was into e-sports Not glamorous, but it's the same muscle I use now closing industrial print orders: get the process right, every time, even when no one's watching.
AI as a force multiplier, not a replacement
This is the one thing I've repeated more than anything else on this site, so it gets its own chapter.
I even say this out loud in interviews: I want employers to know I use AI to increase output, not to skip the parts of the job that actually require judgment. The code review is still mine. The client call is still mine.