2 ms·
You can call it bad code, but someone wrote that bad code. A few people worked on the same team when the bad code got through the cracks. Someone supervised tha
by ineedasername 6y ago
You can call it bad code, but someone wrote that bad code. A few people worked on the same team when the bad code got through the cracks. Someone supervised that team, etc. And some of those people, or people they know, are still working around you. Technical debt may not be the appropriate term, but there are good reasons to be a little more tactful than saying "I have to fix someone's bad code that broke" so that you can continue to have good working relationships with the people around you.