Calling myself a technologist is really about my obsession with exploration - I can’t rest until I’ve pressed every button, tried every flow, and poked every hidden menu to see what makes the software tick. I install the nightly builds, dig through release notes, and write quick scripts just to stretch an API past its comfort zone. Hardware still keeps me curious - I’ll flip a device over, map its ports, and note how the form supports the function - but it’s the code paths, logic branches, and user journeys that keep me up at night.

That curiosity only matters because I turn it into something useful. After I’ve stress-tested a tool from every angle, I translate the insight into tighter workflows and products that feel inevitable the moment you touch them. I loop through explore, learn, build, repeat, because transforming raw curiosity into real-world progress is simply how I’m wired.