Why 'Temporary' Code Fixes Become Permanent Architectural Problems

A software developer recounts how a quick REST-based pricing integration, built under a tight deadline, became a recurring liability when the upstream provider switched transport protocols three times in five months. Each migration — from REST to Kafka to MQTT — required rewriting not just the integration layer but all downstream business logic that had absorbed the transport assumptions. The core issue was not the initial shortcut itself but the absence of an owner, deadline, or ticket to revisit it, allowing it to quietly become load-bearing. The author argues that separating business logic from transport mechanisms through a defined interface would have confined each migration to a single implementation swap. The piece advocates for compiler-enforced module boundaries that let transport layers change without touching stable domain logic.