Hacker News new | ask | show | jobs
by lbriner 1487 days ago
Unless I've misunderstood, I don't like this proposal. To me:

Scenario 1: The code needs doing as part of the work I am doing. Solution: Do it before your current branch is merged otherwise your story is not complete.

Scenario 2: The code will eventually need doing but not now. Raise a task/ticket. Don't pollute the code with things that might never get done. We intended to remove a load of old code previously and haven't done it in 2 years because it isn't a problem.

I don't understand why you want to carry on working but hold back the entire codebase until the second piece of work is done.

1 comments

As I understand it, this is a forced reminder for scenario 1; to ensure the other change is also made before merge.