Why I Rewrote My Site Three Times (And What I Learned)
A brutally honest post-mortem on over-engineering a static blog. Sometimes the best stack is the one you already know.
Thoughts from someone who debugs at altitude and writes about the spaces between commits. Building things, climbing things, writing about all of it.
What happens when you decide to dogfood your own trail-planning app on a 3-week trek through Patagonia? Spoiler: bugs look different at 3,000m.
read_article() →A brutally honest post-mortem on over-engineering a static blog. Sometimes the best stack is the one you already know.
Every trail has edge cases. Every camp has a dependency chain. Turns out mountaineering and architecture have a lot in common.
From a café in Lisbon to a tent in Kyrgyzstan — the exact hardware, software and systems I use to stay in flow on the move.
I spent a week alternating between writing code and holding my breath underwater. Surprisingly related pursuits.
A weekend project that got out of hand. GPX files, elevation APIs, LLMs, and way too much terminal time.
Not a productivity hack. Just a quiet morning, a dark terminal, and the strange clarity that comes before the world wakes up.
I work remotely so I can be anywhere. Here's where the recent dispatches are coming from — and where I'm headed next.
See all adventures →