• rumba@lemmy.zip
    link
    fedilink
    English
    arrow-up
    25
    ·
    6 days ago

    You could most likely find some damn spicy contracts. The real question is, is it worth it?

    You’re going to retrofit some old code to fix an upcoming date bug, or try to make some changes wrapped around security vulnerabilities. But these systems we’re relying on, they’re in banks, air traffic control, and in hospitals, we’re not just depending on these boxes but critically depending on these boxes. There’s almost nobody sitting around to give you a second set of eyes on the code, probably almost nobody capable of doing proper QA on the systems you’re working on.

    • tisktisk@piefed.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 days ago

      Every attempt at dissuading me only makes the fun of the challenge more enticing.

      None of this matters as I have no work experience–only hobby crafting.
      My point is that there will always be people willing to try and the more you tell us “you don’t want to” the more us not so privileged with work-experience continue dreaming with deeper allure

      • rumba@lemmy.zip
        link
        fedilink
        English
        arrow-up
        5
        ·
        5 days ago

        Oh, I’m not trying to talk you out of it, I’m just making sure that you see all sides of the scenario.

        I looked at some of the Y2K patches, I don’t strictly know cobol either , but it’s not that hard to read.

        You’d think that code lying around would be refined as they had limits on space and everything was so mature. It’s still pretty trashy :)