Field notes
Practical notes on AI products, CTO decisions, and the platforms that keep them reliable.
Latest field note
A practical framework for deciding which parts of an AI product should be custom, bought from a vendor or assembled around proven services.
Read the articleCompare managed hosting with an engineering handover, including ownership, support, security, costs and the exit plan you should demand.
The honest cost of an AI product depends less on screen count than on uncertainty, integrations, data, risk and the standard required at launch.
A compelling AI demo proves a possibility. Production software must also be secure, observable, affordable and dependable when reality arrives.
A PRD is a strong starting point, but a responsible software quote must resolve the assumptions that control scope, risk and delivery.
Use these 15 questions to expose the product, technical and delivery assumptions that must be resolved before development starts.
AI has made code faster to produce, but dependable software still requires product judgement, verification and operational ownership.
AMPD and CarBuddy AI sit at different points in the customer journey, but they keep teaching the same lesson: the hard part is not…
Sometimes the universe decides that one production incident isn’t enough. It needs to stack them like Russian dolls, each one revealing another surprise when…
In DevOps, the big outages rarely come from big failures. They come from the tiny things—small enough to slip past everyone’s radar, big enough…
Working on something difficult?
