Photography is my way of resetting my visual perception. When writing code, everything is deterministic, logical, and composed of syntax trees.

Behind a 35mm lens, the world is chaotic, fleeting, and governed by light. I love wandering through quiet alleyways past midnight with an old mechanical rangefinder, looking for unexpected reflections, lonely diner signs, and geometric architecture. Developing physical film taught me patience — you can't hot-reload an exposure.

There is a unique adrenaline rush in assembling a team of three engineers, picking an ambitious problem from scratch, and having a working production deploy live 36 hours later.

I actively participate in university and regional hackathons, both as a builder and a mentor for junior developers. These high-pressure sprints taught me how to triage technical trade-offs, decouple mission-critical paths, and build intuitive user interfaces under tight constraints.

As developers, we touch the keyboard for 8 to 12 hours every day. Treating that primary input device like a commodity felt wrong.

Four years ago, I fell down the rabbit hole of custom mechanical keyboards: designing PCBs, soldering microcontrollers (RP2040), flashing QMK/ZMK firmware with custom layers, and fine-tuning switch acoustics. Building hardware with your hands connects physical physics to software triggers.