Classification Notice for One Line Fix Expansion
Formal notice that a one-line code change has been reclassified as an open-ended cleanup requiring a separate branch.
Classification Notice
Re: One Line Fix Expansion Subject Class: Developer Behavior, Scope Drift, Recurring Classification Level: Established Pattern
What Is Being Classified
The behavior herein classified refers to any instance in which a developer begins with a documented, contained, single-line repair and subsequently uncovers an amount of adjacent cleanup sufficient to threaten the original delivery window.
The developer did not plan this. The developer did not want this. The developer opened the file in question, made the repair, and then saw the rest of the file.
Why This Requires Classification
One line fix expansion exists at the intersection of two separately rational impulses: the impulse to fix the thing that is broken, and the impulse to leave a space better than you found it. Each impulse is professionally defensible. Together, they produce a situation in which neither the fix nor the cleanup is fully complete and the original ticket is technically still open.
The adjacent cleanup was not invented by the developer. The adjacent cleanup was pre-existing. The developer made it visible by interacting with the surrounding code, which had been quietly accumulating inconsistencies since a period the developer was not present for and cannot be held responsible for, but now cannot avoid knowing about.
Procedural History
The first occurrence of one line fix expansion is reported as an isolated event. The fix was completed. The surrounding cleanup was deferred. A note was left.
On the second occurrence, the cleanup was begun. The cleanup uncovered a third area requiring review. That area was deferred with a second note.
By the fifth occurrence, the developer had developed a personal taxonomy for deciding which adjacent issues could be ignored. The taxonomy is not documented. It lives in the developer's judgment. It will not transfer when the developer changes teams.
Current Status
One line fix expansion is considered stable. It is not considered desirable. It continues because the alternative, ignoring visible problems in the file you already have open, is considered by most developers to be a form of professional negligence, which is a standard that the developers themselves invented and continue to enforce without formal authority.
Administrative Note
The original fix is in production. It is working correctly. Separately, there is a branch.