Failure Cost Asymmetry
Failure Cost Asymmetry states that AI tool efficiency is measured by the speed of discarding bad attempts rather than syntax typing speed.
“Progress in software engineering is measured by minimizing the cost of discarded hypotheses.”
Evaluating AI tools purely on token generation speed ignores the primary cost driver of software development: human debugging and state cleanup overhead. Making failure cheap is the only mathematical prerequisite for scaling agentic systems.
Multi-Hop Causal Traversal Engine
Explore how concepts dynamically feed into each other across 1-hop, 2-hop, and 3-hop transitive relationships. Click any node to navigate the causal highway.
Failure Cost Asymmetry
Failure Cost Asymmetry states that AI tool efficiency is measured by the speed of discarding bad attempts rather than syntax typing speed.
Direct Relationships (5)
Transitive Neighbors (Connected via Hop 1)
Extended Causal Ripple Effects
Richard Ewing’s Research Thesis
The model matters enormously, but the environment determines what happens when the model is wrong.
Why This Specification Exists
Teams buy AI coding tools based on typing speed demos and suffer negative ROI from debugging.
Measuring lines of code written per engineer per day.
Lines of code ignore the asymmetric cost of untangling bad generated code.
An economic framework evaluating tools on hypothesis discard latency.
What Changes If You Believe This?
Engineers fearlessly experiment because failed branches are discarded in seconds.
Prevents sunk-cost engineering traps on hallucinated architectural approaches.
Increases the velocity of validated product explorations.
Ensures unverified code is wiped cleanly before contaminating repositories.
Recommended Action by Role
Measure how easily your engineers can discard failed agent attempts.
Copilot ROI Calculator
Quantifies team ROI accounting for human review and cleanup overhead.
Latest Publications & Research Activity
Most Companies Shouldn’t Be Using Autonomous Coding Agents Yet
The AI Coding Tool Battle Is Moving Somewhere More Important Than Code
How Does Meta’s Muse Code Compare to Other AI Coding Tools?
Frequently Asked Questions
Q:What is Failure Cost Asymmetry?
The economic principle that minimizing the cost of discarding bad software attempts creates more developer velocity than faster code generation.
Q:How do engineering teams reduce failure costs?
Through ephemeral Git worktrees, automated compiler checks before human review, and append-only state recovery.
Canonical Specification Origin
Developer ROI is maximized by making failure cheap to roll back.
Corpus Interconnections
Richard Ewing artifacts developed around this canonical framework, including publications, execution tools, and diagnostic models.
External Adoption & Peer Citations
Documented instances where independent researchers, engineering teams, and publications have cited, implemented, or referenced this concept outside Richard Ewing’s ecosystem.
External Evidence: No independently verified references recorded yet.
This concept is part of Richard Ewing’s original baseline canon. External citations and implementations are added only upon rigorous empirical verification.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
Recommended Citation
Ewing, R. (2026). "Failure Cost Asymmetry." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/failure-cost-asymmetry
@article{ewing_failure_cost_asymmetry,
author = {Ewing, Richard},
title = {Failure Cost Asymmetry},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/failure-cost-asymmetry}
}