• MelodiousFunk@kbin.social
    link
    fedilink
    arrow-up
    14
    ·
    1 year ago

    I have seen critical enterprise applications run in VBA in excel.

    I wrote one of them. It replaced periodically writing down application outputs on paper and sounding the alarm if something went pear-shaped. It wasn’t my job to develop software but I didn’t want hand cramps to be my job, either. I had vague ideas about how to do what I wanted to do with Excel so I poked at it and googled until it worked. More than a decade later, I’m no longer there but that freakin spreadsheet is still running 24/7, being proudly showed off during tours of the facility.

    I will cackle if MS ever pulls the plug on VBA.

    • Dave@lemmy.nz
      link
      fedilink
      English
      arrow-up
      12
      ·
      1 year ago

      Your story is pretty typical in my experience. No one hires a dev team to build a VBA tool (except the occasional MS Access tool). It’s normally someone doing the work who works out how to do a basic macro to make it quicker, and it grows from there.

      • MelodiousFunk@kbin.social
        link
        fedilink
        arrow-up
        8
        ·
        edit-2
        1 year ago

        Indeed. In my case, I fought through managerial malaise and turned the entire process on its ear. But even after the approach proved its worth, they refused to put a dev resource on it. It became my problem 24/7.

        Remember kids, being good at something outside of your job description means it’s now your job. If the boss refuses to compensate you for it, slap it on your resume and find someone who will.