← Back to context Comment by inamorty 8 hours ago "Load bearing bugs" 2 comments inamorty Reply drzaiusx11 5 hours ago It really is incredible how frequently these occur in everyday codebases of sufficient size. svieira 4 minutes ago We actually have a constant in our codebase to mark such bugs. You found one? Put it inside an: if (PREFER_EXISTING_BUGS_TO_NEW_ONES) { theOldBehavior(); } else { theNewBehavior(); } Then, if we ever go to do a v2 of the thing, we can review these existing "load bearing bugs" and see if they make sense to change.
drzaiusx11 5 hours ago It really is incredible how frequently these occur in everyday codebases of sufficient size. svieira 4 minutes ago We actually have a constant in our codebase to mark such bugs. You found one? Put it inside an: if (PREFER_EXISTING_BUGS_TO_NEW_ONES) { theOldBehavior(); } else { theNewBehavior(); } Then, if we ever go to do a v2 of the thing, we can review these existing "load bearing bugs" and see if they make sense to change.
svieira 4 minutes ago We actually have a constant in our codebase to mark such bugs. You found one? Put it inside an: if (PREFER_EXISTING_BUGS_TO_NEW_ONES) { theOldBehavior(); } else { theNewBehavior(); } Then, if we ever go to do a v2 of the thing, we can review these existing "load bearing bugs" and see if they make sense to change.
It really is incredible how frequently these occur in everyday codebases of sufficient size.
We actually have a constant in our codebase to mark such bugs. You found one? Put it inside an:
Then, if we ever go to do a v2 of the thing, we can review these existing "load bearing bugs" and see if they make sense to change.