Hike. Travel. Code.
Recent musings...
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 assistant implementations consistent—and what still requires human judgment.
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.
Baker Lake
