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...
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.
From Y2K to AI: 26 years of figuring things out
From Y2K fixes and Visual Studio to mapping systems and Taproot: how 26 years of full-stack engineering shapes my approach to building software with AI.
We put our backlog in Git. Was that a good idea?
Why I keep Taproot’s backlog in Git, how it compares with GitHub Issues for AI-assisted development, and what we’re learning as we build Trellis.
Building Taproot I/O
I started building Taproot I/O because I wanted the coolest web platform on the planet, and WordPress's bloated ecosystem wasn't it.