• SpeakinTelnet@programming.dev
    link
    fedilink
    arrow-up
    47
    ·
    16 days 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
      10
      ·
      16 days 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
        5
        ·
        15 days 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
          14 days 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”.

    • sorval_the_eeter@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      16 days ago

      Nice. You can put that on your resume so you can get more of those kinds of jobs.
      (/s. I like excel to a point but i really feel your pain too-- and fuck vba)

      • FizzyOrange@programming.dev
        link
        fedilink
        arrow-up
        5
        ·
        16 days 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.