Building thoughtful technology, one project at a time
Most statements of work were written for a project where the model never appears. This is a practical look at the provisions a small consultancy should carry into every engagement now that AI tools sit inside ordinary delivery work — covering data handling, model disclosure, output ownership, usage-based cost creep, and the client's right to take the work in-house.
A polished demo can convince a client that software is magic — and leave them unprepared for the ordinary work of running it. This piece outlines a wiring-first approach to demonstrations for nontechnical stakeholders, with a practical checklist for showing what is real, what is mocked, and what will fail first.
Software drift rarely announces itself. It accumulates through renewals, handoffs, and good intentions. This guide outlines a practical review process for small teams that want visibility and intention over the tools they depend on in 2026.
Most migration war stories end in outages and regret. This one ends with a handshake, a working system, and a lesson no framework documentation will ever teach you. A look back at the engagement that reshaped how I approach consulting.
Every codebase eventually changes hands, and the moment of transition reveals more about a team's craft than any launch ever could. This piece examines the quiet discipline of building for a successor you will never meet — from naming conventions to the etiquette of the final walkthrough.
The technology industry celebrates builders and quietly overlooks the engineers who keep systems alive. Drawing on two legacy rescues, this piece argues that stewardship is the more valuable — and rarer — skill, and offers a checklist for finding a caretaker before you sign a contract.
Every independent technologist eventually confronts the same question: where does billable expertise end and community goodwill begin? After a decade of consulting, I've landed on a ledger that works — and it's more generous than you might expect.
Some of the most consequential work in my career began as a Saturday-morning experiment with no roadmap, no budget, and no expectation of survival. This is a look at why small, time-boxed builds outperform ambitious plans — and how to know when a throwaway project deserves to grow up.