What years as an SDET taught me about building agents
The habits that make failures reproducible and success measurable matter even more when software chooses its own next step
Read the outlineArchitecture, evaluation, and the decisions behind reliable agents
The habits that make failures reproducible and success measurable matter even more when software chooses its own next step
Read the outlineModel behavior is one part of the system — deployment, observability, interfaces, and failure handling determine whether the capability is useful
Read the outlineEarly work in games offers a particular education in state, performance, and users who take paths the design never anticipated
Read the outlineA successful demonstration and a reliable system provide different kinds of evidence
Read the draftA sequence of reasonable actions can still produce an unreasonable result — the transitions deserve their own tests
Read the outlineThree stages of an engineering career, connected by the work of understanding systems when they leave the expected path
Read the outlineA practical boundary between checking the model, checking the service, and checking the application that depends on both
Read the draftA bad result might come from the model, the context, the orchestration, or the infrastructure — debugging starts by separating those possibilities
Read the outlineAggregate results can look healthy while a small but important class of failures remains invisible
Read the draftUnexpected behavior is useful evidence about the assumptions built into a system
Read the outlineState that is easy to create can be difficult to inspect, restore, or reason about
Read the outlineA candid account of the distance between wanting to work on games and understanding the day-to-day engineering work
Read the outlineBefore asking whether an agent passed, decide what evidence would make an answer correct
Read the draftThe value of a failure depends partly on whether another engineer can investigate it
Read the outlineCompletion, escalation, and unnecessary continued action are distinct behaviors that need distinct evaluations
Read the outlineSome testing habits transfer directly to AI development — others need a different definition of coverage
Read the outline16 essays in development · Dates refer to drafts, not publication
Working demonstrations of agent behavior, decision-making, and evaluation
Experiments will appear here as they are ready to share
IN DEVELOPMENTI build autonomous AI systems, with a focus on the engineering decisions that make them useful and dependable
My work sits at the frontier of AI software development: designing systems that act, use feedback, and execute toward a goal
LinkedIn