Key Facts
- ✓ DebtBomb is a CLI tool that attaches expiry dates to temporary code.
- ✓ Expired code fails the CI pipeline until removed or the expiry is extended.
- ✓ The tool can automatically create Jira tickets with file paths and code snippets.
- ✓ It supports notifications via Slack, Discord, and Microsoft Teams.
- ✓ Users can configure warnings for code expiring in 7 days.
The Problem with Temporary Code
Every software engineer is familiar with the temporary hack. It is the quick fix deployed to meet a deadline, marked with a comment like "TODO: remove later" or "just for this release." However, these temporary solutions often outlive their intended purpose, slowly becoming permanent fixtures in the codebase.
Over time, the original context is lost. No one remembers why the hack exists, yet it continues to ship to production. This accumulation of undocumented, temporary code creates significant technical debt. A new tool, DebtBomb, aims to make this debt explicit and enforceable.
Introducing DebtBomb
DebtBomb is a small CLI tool designed to prevent temporary code from becoming permanent. Instead of relying on free-form text comments, the tool requires developers to attach an expiry date to temporary code markers.
The mechanism is straightforward but strict: when the expiry date passes, the CI (Continuous Integration) pipeline fails. The build will not succeed until the code is removed or the expiry date is intentionally extended. This forces teams to address technical debt proactively rather than letting it linger.
Key features of the tool include:
"In most codebases I’ve worked on, temporary hacks... slowly become permanent."
— DebtBomb Developer
Visibility and Ownership
While failing a CI build is an effective deterrent, it does not always solve the underlying issue of ownership. To address this, DebtBomb recently added a suite of integrations designed to make expired debt visible and owned.
When a debt bomb expires, the tool can automatically create a Jira ticket. This ticket is populated with critical context, including the file path, the owner, the reason for the hack, and the code snippet itself. This ensures that the technical debt is formally tracked and assigned.
Furthermore, the tool can send notifications to communication platforms like Slack, Discord, and Microsoft Teams. To prevent "surprise breaks," developers can configure "expiring soon" warnings, such as alerts sent 7 days before the code is set to expire.
Validation and Feedback
DebtBomb is currently in its early stages of development. The creator is actively seeking to validate whether this approach genuinely improves how teams handle "temporary" code compared to existing methods.
The tool is being evaluated against standard practices such as:
- Traditional TODO comments
- Static analysis linters
- Manual ticket creation
Feedback is particularly sought from developers who have managed tech debt in long-lived codebases or environments with heavy CI usage. The goal is to determine if automated enforcement and integration provide a tangible workflow improvement.
Looking Ahead
DebtBomb represents a shift from passive documentation to active enforcement regarding technical debt. By linking temporary code to hard deadlines and automated workflows, it attempts to solve the problem of "code rot" at the source.
As the tool matures, its success will depend on adoption rates and the feedback from the developer community. If successful, it could offer a new standard for managing the lifecycle of temporary code in complex software projects.
