Writing / Field notes
Working ideas, made inspectable.
Notes from building products, leading technical systems, recovering difficult programs, and making AI-assisted engineering more governable.
7 published notesBuild a small lab for your browser-testing tool
Build a controlled fixture and answer key, retain incomplete runs, and test the scorer before using it to compare browser-testing tools.
Before building a roadmap item, test the premise behind it
Use one proposed parallel runner to distinguish a plausible feature from a problem your records can actually establish.
Plant the bugs yourself: how to find out if your testing tool cries wolf
Use planted defects and working cases to distinguish useful findings from false alarms, with a small Jevitate evaluation and its limits.
Keep end-to-end tests useful as your app changes
When a browser test breaks after a screen changes, preserve the user outcome before repairing the steps. A worked order-flow example shows what to check.
Write a coding-agent handoff you can review
Use a bounded slug-helper example to define scope, acceptance checks and the evidence needed before applying a change.
Catch a failed save even when the page says Saved
Use Jevitate to investigate a misleading success message, inspect browser evidence, and recheck a fix against the failure that prompted it.
Before hiring more engineers, find where delivery gets stuck
Trace one recent feature through your team to distinguish a capacity shortage from coordination, architecture, and product-decision bottlenecks.