FIELD NOTE / X
Measure the second change.
The short film, the complete written thought, and the evidence behind it.
The X conversation link will follow its public release.
Measure the second change.
Video caption
Measure the second change. The cost appears in affected contracts and review cycles. First-demo speed is only one input. Narration uses Eric's authorized AI voice clone. #EricFieldNotes
Full written post / accessibility read
An agent can draft an approval app quickly. The harder question comes when policy adds a new approval mode. If checks were copied into controllers, jobs and exports, one small business change becomes several uncertain edits.
Do not invent a universal time penalty. In a disposable comparison, count files touched, independent contracts affected, protected tests, review rounds and customer-state readbacks for the same second change.
Place approval rules behind one owned boundary in one fixture and duplicate them across routes in another. Ask an agent to implement the same new mode in both, then test exports and notifications.
Keep the fixture, expected states and reviewer time visible. Do this because useful engineering speed is the time to a maintainable accepted outcome, not the time to the first plausible patch.
Narration uses Eric's authorized AI voice clone.
#EricFieldNotes
Four-beat scene transcript
1. Measure the second change.
An agent can draft an approval app quickly. The harder question comes when policy adds a new approval mode. If checks were copied into controllers, jobs and exports, one small business change becomes several uncertain edits.
Visual: The first green demo conceals future change spread.
2. Speed at draft time is incomplete.
Do not invent a universal time penalty. In a disposable comparison, count files touched, independent contracts affected, protected tests, review rounds and customer-state readbacks for the same second change.
Visual: The cost appears in affected contracts and review cycles.
3. Compare modular and duplicated paths.
Place approval rules behind one owned boundary in one fixture and duplicate them across routes in another. Ask an agent to implement the same new mode in both, then test exports and notifications.
Visual: Run the same requested change through both fixtures.
4. Judge accepted change cost.
Keep the fixture, expected states and reviewer time visible. Do this because useful engineering speed is the time to a maintainable accepted outcome, not the time to the first plausible patch.
Visual: First-demo speed is only one input.
Research and claim limits
- DORA 2025 State of AI-assisted Software Development (S225)
- GitHub Copilot Agents application card (S226)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.