• Arghblarg@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    28 days ago

    I was on a project where a co-worker left and his son was onboarded a few years later; he seemed much more chill than I when we were both working on an issue and it dawned on me that he was literally fixing (well, not really a defect just an update) his Dad’s code. Heh.

  • Droggelbecher@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    28 days ago

    Tangential, but I’m working with some code that started out in the punch card era (I’m doing particle physics, it’s in fortran)

  • Lifter@discuss.tchncs.de
    link
    fedilink
    arrow-up
    0
    ·
    28 days ago

    Impressive to work that long on something and not change the code at all. The mom('s team) was either very competent at writing configurable code or very good at pretending to work.

    • Treczoks@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      28 days ago

      With such a codebase, once it is settled to a certain point, you stop adding things. You write new things, and carefully interface with the old stuff.

      Imagine a bank. Their software core is usually neolithic, i.e. written in COBOL or even worse, FORTRAN. You don’t add the “online banking” or “web client” interface in the original language. You add them in something more contemporary, which interfaces to the neolithic core via files, pipes, libraries, whatever, and translate it into a frontend as needed. As long as the core works, nobody needs to touch it.