disposable design
person concept tool org talk claim — click a node to jump to its page; hover an arrow for the relation
A workflow philosophy in AI-assisted development where tools, scripts, or fine-tuned models are built for a single specific purpose and then deliberately discarded rather than maintained or generalized.
Core Concept
Disposable design represents a shift in how practitioners think about the cost-benefit of building software tools. Because coding agents dramatically lower the effort required to create custom tooling, it becomes practical — even preferable — to build narrow, purpose-fit solutions that are thrown away after use rather than investing in reusable, generalized infrastructure.
Eve Bouffard (YC's Head of Design) explicitly advocates for this approach, calling out specific examples during her talk as "another great example of disposable design" 18:47. She frames it as a muscle to develop: the habit of spinning up a custom model or tool, tweaking it precisely for the task at hand, and discarding it once the work is done — "Building this muscle of oh yeah I can just like build a model for myself and then tweak everything and then when I'm done with it I discard it in one shot" 6:21.
Why It Matters
The concept challenges traditional software engineering instincts around reusability and DRY (Don't Repeat Yourself) principles. When the marginal cost of creating a tool approaches zero via AI coding agents, the calculus changes: over-engineering for reuse becomes a liability rather than an asset. Single-use fine-tuned models are cited as a concrete application — built, used for their specific transformation or task, and then discarded rather than versioned and maintained.
Points of Disagreement
No speakers in the available material argue against disposable design. The concept is presented entirely approvingly, though it implicitly contrasts with conventional software development culture that prizes reusable abstractions.