Hike. Travel. Code.
I'm Jereme Evans. I've been building software for 26 years, and these days I'm building Taproot I/O. This site is where I write about that work, and about the hikes and trips Euri and I take when I step away from the keyboard. Browse by code, hikes, or travel.
Recent musings...
Antigua, Lake Atitlán and El Paredon: our Guatemala itinerary
Our Guatemala route from Antigua to Lake Atitlán to El Paredon, how we got between stops, and what I'd change, including whether the beach is worth it.
San Pedro, San Juan, or San Marcos: which Lake Atitlán town?
We slept in San Pedro, shopped in San Juan and ate our way through San Marcos. Here's which Lake Atitlán town I'd pick as a couple next time.
Mount Washington vs Mount Ellinor: which Olympic peak near Hoodsport?
Mount Washington and Mount Ellinor share a road above Hoodsport and almost nothing else. Distance, gain, scrambling, passes and goats, compared.
Why I avoid third-party packages, and how AI helps
Why I write or vendor small pieces of code instead of adding third-party packages, how AI makes that practical, and when a package is worth it.
Contract-driven development: How we keep Taproot’s frontend and backend in sync
How Taproot uses protobuf contracts, generated clients, and drift checks to keep its frontend and backend in sync while building with AI.
Why documentation-first development helped us build with AI
How documentation-first development helped us build Taproot with AI, using working examples, shared language, and checks that keep docs connected to code.
How we enforce coding standards
How lint rules, architecture tests, and contract checks keep AI-written code consistent with our standards, and which decisions still need a person.
Why moving to a monorepo made AI-assisted development easier
How a monorepo made AI-assisted development easier on Taproot: fewer package releases, coordinated changes, migration costs, and the boundaries we kept.