|
|
|
|
|
by tdeck
1283 days ago
|
|
I'm not sure this pisses me off "to my core", but I've seen so many teams stop fixing bugs in something because they're writing a replacement that's supposedly going to be done in 6 months and will have none of those bugs. 2 years later the V1 is still the only solution that exists, and it's been allowed to rot while everyone suffered through the same bugs for 2 years. This happens most often when a team inherits a codebase they aren't familiar with and aren't excited about learning. |
|