- 10When are specifications not enough?
- 11Where is the state of the work kept?
- 12Who prepares a change before coding starts?
- 13What does impact analysis tell you, and when does it run?
- 14How do coding agents use the graph?
- 15How is each change checked, and how does the graph stay current?
- 16Who decides which work agents do?
- 17How do managers see what people and agents are doing?
- 18What happens across many products?
- 19What about existing systems and technical debt?
- 20What changes for the team?
- 21What results have teams seen?
Home / Follow the story / Scene 3: The Manual Translation Tax
Transcript
3. The Manual Translation Tax
The Manual Translation Tax is the recurring cost of knowledge and context lost at each handoff across roles, artifacts and tools, as documents, messages and memory become decisions and code. Every translation takes time, and every translation loses some information. A coding agent makes writing code faster, and leaves the tax where it is. The team's time goes into paying the tax, so faster code generation does not make the team faster. The tax has three components, and all three appear even on disciplined teams with good tools. The first component is ambiguity: the same words mean different things to different people. A product owner writes "let users save their search so they can return to it later". The frontend developer stores the search in the browser, the backend developer stores it in the database, and the QA engineer tests for a confirmation message. The difference surfaces in code review, and two weeks of work are partly redone. The second component is non-persistence: knowledge that was never written down is lost when the person who holds it leaves. When a senior engineer leaves, the team spends months rediscovering what she knew, usually when something breaks. A coding agent loses its knowledge the same way, because every new session starts with no memory of the last one. The third component is non-traceability: nothing records which parts of the code depend on a feature the user sees. When the alert frequency on saved searches changed from daily to weekly, some customers received both emails, because a worker in another repository still sent the daily ones. Nothing linked the alert frequency feature to that worker, and finding the cause took two days. The usual response to the tax is to write more documentation. On one platform team, roughly 40% of the architecture pages sampled were materially out of date by the end of the year. More documentation adds more text to translate, and the new text goes out of date in the same way. Removing the tax requires changing how the knowledge is recorded.
On the site: The Manual Translation Tax: The Cost, Named · How It Shows Up in a Sprint · The Three Components of the Tax
Choose a path
The full video in six parts and an appendix, one part at a time.