Discardable Software: When Code Is Cheap Enough to Throw Away

Business Pill 17 · Software you can throw away

When software becomes cheap enough to throw away, the logic of building it reverses. The value moves from the code to what has to stay true.

A short explainer video. The numbers in it are round numbers for illustration.

Software Has Always Been Expensive

Software has always been expensive to write, so we wrote it once and used it for years. One program had to serve thousands of people to justify its cost. Everyone got the same screens and the same buttons.

What AI Changes

AI changes the first step. A model can now write a working program in minutes, for almost nothing. And when writing is nearly free, the logic reverses. You no longer need thousands of users. One user and one task is enough.

These are programs made for the moment, used and thrown away. This is discardable software. It is more like a note you jot down than a book you publish.

A Worked Example

The video uses round numbers. A custom tool takes a developer two weeks and costs $10,000. It must be used 1,000 times to be worth it. Spread over those uses, that is $10 each, which is this publication’s arithmetic on the example.

The same tool, generated in a minute, costs about a dollar. It can be used once and still be worth it.

Bar chart: a custom tool costs about 10 dollars per use over 1,000 uses; a generated tool costs about 1 dollar for one use
Round numbers for illustration. The $10 per use is this publication’s arithmetic on the video’s example.

What Still Has to Last

Not everything becomes discardable. The data must last. The rules of the business must last. And the checks that tell you the program did the right thing must last. The code in between can come and go.

So the value moves away from the code itself, which anyone can now generate, toward what stays the same: the record of what happened and the definition of what is correct.

Three Questions to Ask

  1. Which of our software has to be permanent?
  2. Which could be generated when it is needed?
  3. What has to stay true either way?

See It in the News

Karpathy’s Case for Discardable Software. A news piece on the same idea from a practitioner’s argument.

How This Concept Connects

Layer 4 of 8 · Agents & Workflows, on the Business Engineer Concept Map

AI Evaluation as AcceptancOperating LeverageSystem of RecordVerification CostGenerative UIDiscardable Software
  • Discardable Software builds on AI Evaluation as Acceptance Test. The checks that tell you the program did the right thing must last even when the code is thrown away.
  • Discardable Software contrasts with Operating Leverage. Software once had to serve thousands of users to justify its cost; near-free code reverses that build-once logic.
  • Discardable Software builds on System of Record (lesson unlocks soon). When code becomes disposable, value moves to what must last: the data and business rules kept in one place.
  • Verification Cost (lesson unlocks soon) constrains Discardable Software. Code that is cheap to make is not cheap to check, so checking caps how freely throwaway software can be used.
  • Generative UI (lesson unlocks soon) is an example of Discardable Software. A screen the model builds for one question, every time, is software made to be used once, the idea of the discardable software lesson.
Business Engineer framework
Great SaaS Bifurcation
Cheap code reshapes software economics.
Business Engineer framework
From SaaS to AGaaS
From durable software products to agent-delivered work.
See all 143 concepts on one map
Get the full Concept Map as a free poster.
Get the map

More Business Pills

Scroll to Top

Discover more from FourWeekMBA

Subscribe now to keep reading and get access to the full archive.

Continue reading

FourWeekMBA