3 ms·

This reminds me of a lot of devs who don’t bother understanding a working but old system and immediately declare it’s crap that needs a total rewrite :)

• fzeroracer 7y ago
  And sometimes an old system actually does need a total rewrite because it's leaking PII everywhere, prone to completely crashing every couple of years and struggles to interface with automation.
  • Ididntdothis 7y ago
    And very often it would keep working nicely with just a few minor changes.
    • fzeroracer 7y ago
      A few minor changes that never arrive because your company dictates you add new features and functionality than fix tech debt (because tech debt doesn't earn more money). So you have large parts of the codebase which are actively on fire, but not too much on fire that it's costing money yet. Until you run into a hard wall trying to integrate new features that customers request which break the entire system and before you know it, you're still running on C# 3 while all of the other APIs and companies have long upgraded to C# 8 (or switched languages altogether). Then your wildfire turns into a firestorm and your customers start calling in. And they're pissed.