Write Code That's Easy to Delete: The Art of Impermanent Software

The article argues that software should be designed for easy deletion, not just long-term extension.

It recommends keeping code localized, loosely coupled, and behind clear seams so features can be removed safely.

This reversibility can reduce codebase sprawl, lower maintenance risk, and speed up product changes.

Examples include feature flags, adapter layers, interface abstractions, and strangler-fig style migration.