claim candidate goes to: this-edition T town planner
Code is a liability; the future is the smallest code that does the job
Every shipped line is a capability someone may misuse (Log4j; 428 of 1,500 files ran); the next maintainer is an agent; the minimal viable code path.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Where it comes from
- The code you do not ship the argument (newsroom)
- The minimum code below 428 of 1,500 (newsroom)
What it answers in the 2018 book
- Legacy Applications answered outline, Concepts
- Refactoring answered outline, Life Patterns
- The future needs you answered written, Life Patterns
Where it goes
Chapter Controlling your agent: RiskMandate, part Build it without a server (drafting); topic Security for the agent era: least code, supply chain, secrets, learning to hack.
Other ideas proposed for the same chapter: Mandate, reach and the gap: hope versus enforcement, Learning to hack is still how you learn how things work: draw the line where the attacker is, The secret goes from the drop into the tool, never into the chat, Security experience is what lets you ship with known gaps: list them, match them to the reader, say what would change the call.
Node idea:code-is-a-liability in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.