no-workarounds

To stop developers from using workarounds, enforce a root-cause fixing process that requires tracing failures to their underlying issue before applying changes. This prevents symptom-patching and compounding technical debt across your codebase.

A root-cause fix addresses the underlying failure directly, while defensive code scatter is an anti-pattern workaround that suppresses errors across multiple locations. True root-cause resolution isolates the issue instead of hiding the failure signals.

A workaround during debugging is acceptable only when the root cause is external and upstream is uncertain, provided the business impact justifies shipping. The workaround must be isolated with tracking documentation and test canaries.

Detect anti-patterns like error swallowing and timing hacks during code review by applying a structured workaround-detection gate. This process verifies that proposed changes resolve the actual problem rather than silencing signals or evading type systems.

Yes, this root-cause fixing approach works across different languages and frameworks. It applies broadly to debugging, architectural decisions, and code review by enforcing patterns that reject monkey patching and lint suppression universally.