There's a moment on every climb — somewhere between the burn in your legs and the first glimpse of the summit — where everything simplifies. The backlog, the bugs, the meetings — they all fall away. It's just you, the trail, and the next switchback.
Living in Seattle puts me at the doorstep of some of the most dramatic terrain in the lower 48. I spend my weekends chasing ridgelines in the Cascades, losing myself in the alpine meadows of the Enchantments, and planning multi-day backpacking routes through the Olympic wilderness. Mount Rainier is the permanent backdrop — a reminder that the next challenge is always on the horizon.
There's a parallel between engineering and mountaineering that I find deeply resonant: both demand preparation, adaptability, and the willingness to commit to a route even when the summit's in the clouds. The best days in the mountains — the ones where the weather breaks at exactly the right moment, where you catch alpenglow on Glacier Peak — those are earned, not given. Same as shipping great software.
Pacific Northwest powder is a different breed — heavy, wet, and relentless. When the convergence zone fires and Baker picks up 18 inches overnight, there's exactly one correct response: set an alarm for 4:00 AM and point the car north.
I started riding in Michigan on icy 200-foot "hills" that Washingtonians wouldn't even bother putting a tow rope on. Moving to the Cascades was like upgrading from a kiddie pool to the ocean. The steeps at Stevens Pass, the glades at Baker, the spring corn at Crystal — every mountain has its own personality, and I'm still getting to know them all.
Snowboarding taught me something that engineering reinforced: commit to the turn. Hesitation is what sends you into the trees. Same principle applies to launching a feature, choosing a tech stack, or merging a PR at 4:59 on a Friday.
Most people see coffee as a caffeine delivery system. I see it as a chemistry experiment with delicious results. Making great espresso demands the same discipline I bring to engineering: control your variables, measure your outputs, iterate relentlessly.
Every morning is a micro-experiment. Grind size, dose weight, water temperature, pre-infusion pressure, extraction time — each variable interacts with the others in non-linear ways. A single click finer on the grinder can be the difference between a balanced, syrupy shot with notes of dark chocolate and blueberry and a channel-choked bitter mess.
I keep a shot log. I track extraction yield by TDS refractometry. I've dialed in beans from every major Seattle roaster — Vivace, Elm, Herkimer, Lighthouse — and a few international ones besides. The intersection of applied fluid dynamics and sensory science is genuinely fascinating, and it's made my morning routine something I look forward to with the same intensity as opening a fresh codebase.
Green Lake at 6:30 AM is one of Seattle's best-kept secrets — if you don't count the fifty other runners who also think they're the only ones who know about it. I run the 2.8-mile loop as a daily reset: headphones in, pace steady, mind free to wander through whatever architectural problem I've been stuck on. Some of my best design decisions have happened between miles one and two.
Volleyball is the opposite energy — reactive, explosive, social. There's no time to overthink a dig or plan a spike by committee. You read, you react, you trust your training. I play pickup games around Seattle and it's become one of my favorite ways to decompress. The transition from a solo morning run to an evening at the net keeps my competitive edge sharp without burning me out.
Together, running and volleyball create a rhythm — solitude and community, endurance and burst, contemplation and reflex. It's a balance I try to mirror in my engineering work: deep focus time for architecture, collaborative energy for code reviews and design sessions.