Todo Comment Aging Has Acquired Standing
A comment written without a deadline has been found, by inaction, to constitute permanent policy.
The comment appears on a Tuesday at 11:43 AM, inserted two lines above a function that handles session expiry. It reads: // TODO: fix this properly. No ticket number. No author handle. No deadline.
Nothing happens.
Three weeks pass. A pull request touches the file. The reviewer sees the comment. The reviewer says nothing. The comment is now two reviews old.
This is how a TODO acquires standing.
Scene I: First Encounter
A new engineer joins the team in March. She reads the codebase. She finds the comment. She considers asking about it. She decides that asking about something this old would imply the team had oversight. She leaves the comment in place.
The comment is now one new engineer old.
Scene II: The Audit
In Q2, the team runs a technical debt audit. Someone writes a spreadsheet. The TODO appears in the spreadsheet under a column labeled "Severity." Someone types "Low." Someone types "Known." No owner is assigned because assigning an owner would require acknowledging the comment was not owned before.
The audit closes. The spreadsheet is filed. The comment survives.
Scene III: Institutional Recognition
By August, the comment is eight months old. A senior engineer references it in a design review: "We've known about this for a while." The phrase "we've known about this" retroactively classifies the TODO as shared knowledge rather than deferred action.
This is the moment the TODO stops being a note and becomes a fact.
The governing rule, now clearly in effect: a TODO comment without a deadline gains procedural status once it survives two code reviews without challenge. Its survival is evidence. Its longevity is, apparently, its justification.
Scene IV: The Handoff
The engineer who wrote the comment leaves the company. During his offboarding, nobody asks about the TODO. Asking would require confirming that it remained unfixed for eight months under active development.
His laptop is wiped. The comment is still in production.
Final Entry
A junior developer finds the comment in October. She adds a ticket. The ticket is labeled "Good First Issue." It sits unassigned for six weeks. Someone eventually closes it as a duplicate of a ticket that was itself closed as a duplicate of the original TODO.
The comment remains. It is now the oldest continuous feature of the module.