FIELD NOTE / TIKTOK
The app looks fixed. Replay yesterday's event.
The complete written thought and the evidence behind it. The video edition will follow its public release.
The written argument is here.
This approved TikTok edition is on the journal now. Its video player and original platform link will appear after each public release is verified.
The app looks fixed. Replay yesterday's event.
Video caption
The app looks fixed. Replay yesterday's event. It is a deployment contract across owners. They must know what to ask the agent to repair. #EricFieldNotes
Full written post / accessibility read
In this fictional service, an agent updates a billing-event producer. Its new tests pass and the demo looks fine. Yesterday's events are still in a queue, and one consumer has not upgraded. What happens when the old shape is replayed after the rollout?
A correct local implementation can still be unreleasable if the consumer contract and migration window are unresolved. The engineer has to understand schema evolution, replay, partial deployments and business ownership. The agent may draft a dual-version parser, but nobody should invent the compatibility policy from a green unit suite.
Ask the candidate which saved old event should pass through which consumer version, and what business result would count as success. A strong answer suggests changing the version or parser to ensure the check turns red, then asks the owners how long both shapes must coexist. The interview needs the reasoning, not a built replay harness.
The rule: evaluate fundamentals on system boundaries, not typing. Do this because when the agent's session ends, someone still has to explain, extend and fix the architecture. The person who knows the queue and contract can direct a correction; the person trusting only the demo cannot.
#EricFieldNotes
Four-beat scene transcript
1. The app looks fixed. Replay yesterday's event.
In this fictional service, an agent updates a billing-event producer. Its new tests pass and the demo looks fine. Yesterday's events are still in a queue, and one consumer has not upgraded. What happens when the old shape is replayed after the rollout?
Visual: The old message lives outside the patch.
2. This is not a junior bug hunt.
A correct local implementation can still be unreleasable if the consumer contract and migration window are unresolved. The engineer has to understand schema evolution, replay, partial deployments and business ownership. The agent may draft a dual-version parser, but nobody should invent the compatibility policy from a green unit suite.
Visual: It is a deployment contract across owners.
3. Ask one falsifying question.
Ask the candidate which saved old event should pass through which consumer version, and what business result would count as success. A strong answer suggests changing the version or parser to ensure the check turns red, then asks the owners how long both shapes must coexist. The interview needs the reasoning, not a built replay harness.
Visual: Can an old event produce the intended result?
4. Keep the engineer in the loop for the right reason.
The rule: evaluate fundamentals on system boundaries, not typing. Do this because when the agent's session ends, someone still has to explain, extend and fix the architecture. The person who knows the queue and contract can direct a correction; the person trusting only the demo cannot.
Visual: They must know what to ask the agent to repair.
Research and claim limits
- U.S. OPM: Work Samples and Simulations (S151)
- Google Research, Towards AI as a Collaborative Partner (S155)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.