I stole this from LinkedIn.

  • Gaja0@lemmy.zip
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    17 hours ago

    Old code is insane. The coders at my work don’t want to touch the millions of lines of visual basic 6 and fortran that prop up the company. No loops. No encapsulation. Just assignment and soft validations.

    Co-pilot says that was considered safe back in the day. One team just triple checking things and sending to production. The comments suggest issues I have today have been issues and unaddressed for decades.

    I can’t get the code to compile and you have to pay MS if you want VB6 IDE, so all I can do is look at the ancient texts I barely understand and ponder its implications on my job.

    • zod000@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      5 hours ago

      It was such a clusterfuck and it sucks that you need to work on that code now, but I have a lot of nostalgia for VB. It was really novel and easy to use and quite honestly (IMO) good for what it was. I think I said verbatim “holy shit, a monkey could make a program with this” when I first used VB 4.

      • definitemaybe@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        2 hours ago

        VB is still great. I use it to fully automate a lot of Excel-based tasks, like looping through thousands of Excel files to pull values or update spreadsheets with new features.

        Sure, there are more powerful tools, but VBA is built in and works really well for some tasks like that.