Atty House · 2026 – present
A house that can explain itself
Everything worth knowing about a house is scattered across public records, plans, photos and paperwork, and almost none of it can answer a question.
I build technology products and the systems behind them.
I work across product, software, architecture, AI, infrastructure and technical strategy, usually where the problem is still ambiguous and the path to production isn't obvious. 21 years of it, from early products to systems at significant scale.
Selected work
Yak AI · 2026 – present
Letting customers use a product by saying what they want
Customers give up on menus, filters and forms. Businesses want them to just ask, without rebuilding their product or handing an AI the keys to it.
Latest writing
Software should take the fly-by-wire step
Fly-by-wire moved pilots from moving surfaces to stating intent inside an envelope people designed. Software should take the same step.
Engineering headcount will stop tracking the backlog
Engineering's job becomes building and operating the shared capability that turns approved business requests into production changes, not implementing each one.
When AI writes the code, direction is the job
AI is now good at writing code and tests, but it builds what you point it at. Good direction answers its questions. Great direction helps it make decisions.
How to test whether your AI agent follows instructions
Telling an AI agent how to behave isn't enough. Pair every behaviour with eval scenarios that check it, so changes and model upgrades don't rely on hope.
Now
Building Atty House, which tells the story of a house and answers questions about it with sources. Also Yak AI. Both have people using them.
What I'm focused on