Boring and bulletproof beats impressive and brittle.

Off the clock I chase adventure in most of its forms. If it has wings, wheels, or a sail, I've probably spent many hours behind its controls, and travel to me means a loose plan, a full pack, and the assumption that the good stories start where the itinerary ends.

I'm equally hooked on puzzles. Not just solving them: setting them. A chess position, a stubborn boulder problem, a system that misbehaves, a sudoku that doesn't exist yet. Anything with hidden structure scratches the same itch that pulled me into physics.

Mostly, I like finding out where my limits are and then moving them. The lists below may read as hobbies, but they're really one long experiment in going a little past comfortable, whether the unit is a grade, a rating, or a finish line.

It may all sound like a solo act, but the common thread is connection, and it comes in two kinds. With people: almost everything above is better shared, and the best part of any trip, climb, or match is the company. The second kind is with the world itself: the mountains, the ocean, swimming alongside sharks, sharing a thermal with a buzzard. Nothing resets me like being a small guest in something that big.

Ask people I've worked with and "team player" probably comes up first. I do my best work embedded in a team rather than next to one, and for me that runs on straight answers, promises kept, and genuine interest in what makes the people around me tick.

I treat the human side of engineering as a craft in its own right. How feedback lands, how disagreement stays useful, how a group of sharp individuals becomes an actual team: I study that as deliberately as I study technology. What you get is a colleague who says the uncomfortable thing early and kindly, and who would rather be honestly wrong than politely vague.

I also refuse to build blind. Before anything ships I want to understand the actual problem, the person it's for, and the way it will really be used. Writing the code is rarely the hard part; building the right thing is.

I thrive on ownership: hand me the problem and the context, and trust me with the how. In return you get a high bar, a craft that keeps getting sharper, and everything I learn shared freely, whether that's pairing, mentoring, or an unreasonable amount of documentation.

Underneath it all sits a stubborn optimism about people, a competitive streak, and more energy than is strictly necessary.