4.0 KiB
Shedding Weight
#concept
Summary
thorsten-ball's operating discipline: most of your process exists because humans used to be the bottleneck, and it should be deleted. Not optimized — deleted. "Don't optimize for what looks safe today, optimize for the ability to move fast tomorrow."
Current Understanding
The test for any workflow, feature or artifact: would this exist if agents had always been available? If not, it is weight.
Named casualties from the source:
- Backlogs. Old loop: bug reported → backlog → weeks later someone decides it's worth doing → estimate → maybe fix. New loop: "optimistically spawn these agents, have them parked somewhere, then go through the bug fixes." You no longer estimate whether a bug is worth fixing when the fix ran while you slept. Backlogs are an artifact of expensive humans.
- CI that re-runs the agent's own tests. The agent is already in an isolated sandbox and already ran the tests; pushing so CI can repeat them for ten minutes is waste motion.
- IDE extensions. amp killed its VS Code extension — "who has the editor open anymore?"
- Admin panels and forms. They existed so that no code had to change; changing the code is now cheaper. See build-for-the-agent-not-the-human.
- Local dev environments. Predicted to go away as remote sandboxes take over (async-by-default).
The corporate version is aggressive self-cannibalization: AMP publicly kills its own features and accepts churn from users pushed out of their comfort zone. The commercial logic is that a defensible-looking 2025 product ("single agent in a VS Code sidebar with enterprise permissions and per-line attribution") would have been obsolete within a year.
The honest form of the exercise is his suggested internal doc: "Software Is Dead — Now What?" — be specific about which of your processes only survive because humans used to be the bottleneck.
Evidence
- Backlogs, CI, VS Code extension, "AMP Frontier Corporation," the frontier bet, the suggested internal doc — 2026-07-28-agentic-engineering-10x-developer.
- The same instinct one layer down: killing code without guilt and resetting rather than guilt-merging — 2026-07-14-everything-we-knew-about-software-has-changed, via code-as-throwaway.
Related Pages
- Concepts: code-as-throwaway (the artifact-level version of the same move), build-for-the-agent-not-the-human, async-by-default, explosion-of-internal-software, product-ownership (deciding what should exist is the surviving job), enterprise-ai-reality (the strongest counterweight)
- Entities: thorsten-ball, amp, theo-browne
Contradictions / Uncertainty
- Compliance doesn't shed. In enterprise-ai-reality, CI, audit trails, backlogs and permission systems are frequently the deliverable to a regulator, not overhead. Thorsten is describing a startup on the frontier and never scopes the claim; sebastian's clients cannot install their own tools, let alone delete their pipeline. Status: tentative.
- "The agent already ran the tests" assumes you trust the agent's report of its own run. Nothing in the source addresses a lying or truncated test run — an obvious place for make-more-cheap-code to re-enter.
- Deleting the backlog and "parking agents" replaces one queue with another; the source does not say who triages the parked fixes or what that costs in attention.
Next Questions
- What is the smallest safe version of this for a non-frontier team — which single pre-agent workflow gives the biggest return when deleted first?
- Does shedding weight have a floor for a person rather than a company? The webinar audience's equivalent of "kill your backlog" is unclear. (Proposed 2026-07-28: the audience-facing form is the question "which of your processes only exist because you were the bottleneck?" — carried as thesis T10 in 2026-07-28-webinar-theses, where it is suggested as an opener. Untested on a non-engineer audience.)