• SpeakinTelnet@programming.dev
    link
    fedilink
    arrow-up
    11
    ·
    2 months ago

    Can confirm. Was quite unhappy in my mechanical engineering job, had an opportunity to develop something nice in python, was told we’d do it in excel/vba instead, still unhappy.

    • MajorHavoc@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      2 months ago

      was told we’d do it in excel/vba instead, still unhappy.

      I just threw up in my mouth a little. Fifteen years ago, “I’ll stick to Excel” was a (bad, but) defensible position in data automation. Today that’s just insanity.

      • SpeakinTelnet@programming.dev
        link
        fedilink
        arrow-up
        3
        ·
        2 months ago

        I’m still in a mechanical engineering world so just saying INT and FLOAT has people running away. Excel is the “safe zone” for them, sadly it means that I’ll just be doing the VBA part and oh gawd please get me out of here…

        • MajorHavoc@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          2 months ago

          Yeah. I get that. Gotta do what you gotta do!

          I’ve made some progress at organizations like that by setting up a private workflow in Python “just to check my work”.

      • FizzyOrange@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        It’s cloud based though… Not ideal. I get why they had to do that (they didn’t want to expose people to the Python infra shit show) but it’s still kind of a shame.

        Would be better if they added Typescript support IMO.