3 ms·

Yeah nah maybe fix the bugs before swapping the average COBOL dev for the average Java dev.

• nicman23 2mo ago
  sometimes if the bug exists for enough time it is intended behavior
  • surfingdino 2mo ago
    Indeed, there may even be a whole lot of code that depends on it.
    • wwind123 2mo ago
      Yeah. Bug-for-bug migration is a real thing in large code-bases in the industry. You want to replicate all behavior of the code regardless whether the behavior is a feature or a bug. See Hyrum's Law: https://www.hyrumslaw.com/ https://www.hyrumslaw.com/
    • nkjoep 2mo ago
      Yep, and when it’s about money you don’t want any unexpected.
  • tapland 2mo ago
    Absolutely, and you'll have all kinds of fixes for the symptoms throughout the project. COBOL isn't hard, the tooling around it on old systems are a pain though.
    • Maxion 2mo ago
      Anything running on COBOL to day is a large enterprise system. You'll have reports running in other systems in subsidiary companies that rely on bugs in the upstream cobol code.
  • skissane 2mo ago
    One of the hinges on our front screen door was coming off, the screws were coming loose from the wooden door jam. So I screwed it back on. My wife and son then told me I "broke" the front door. I was confused, I thought I had fixed it Turns out, with the door coming off the hinges, it wasn't closing properly, which meant it was ajar most of the time, so our dog could push it open with her body. Now I'd fixed it, it closed properly all the time, so our dog started whining for someone to open the front screen door for her So I loosened the screws, and hence "fixed" it by breaking it again
    • pasc1878 2mo ago
      So a form of https://xkcd.com/1172/ https://xkcd.com/1172/
    • yomismoaqui 2mo ago
      Ah, the classic load bearing bug.
• vrighter 2mo ago
  hyrum's law applies here