The Deletion Test – The Phoenix Architecture
17 hours ago
- #Code Management
- #System Design
- #Software Engineering
- The 'deletion test' is a diagnostic for software systems: imagine deleting the entire implementation without any fallback; if this causes fear, it indicates that knowledge essential for correctness is only embedded in the code.
- Fear of deletion often stems from missing explicit evaluations, like precise behavior requirements, acceptable failures, invariants, or methods to verify a new version's correctness, making code act as a cache for understanding rather than just an asset.
- As software generation becomes cheap, validation becomes the bottleneck; code should be disposable, with reliance shifted to property-based tests, contracts, invariants, and operational signals that serve as oracles for correctness.
- The goal is to make deletion boring and regeneration safe by externalizing rigor into the surrounding system, ensuring that code is not the sole source of truth but can be replaced without losing understanding of the system.