• @[email protected]
    link
    fedilink
    01 month 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.

    • @[email protected]
      link
      fedilink
      01 month 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)

    • lime!
      link
      fedilink
      English
      01 month ago

      excel has python support now! you may still get away with it

      • @[email protected]
        link
        fedilink
        01 month 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.

        • lime!
          link
          fedilink
          English
          01 month ago

          …like the js infra stuff isn’t it’s own special nightmare?

    • @[email protected]
      link
      fedilink
      01 month 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.

      • @[email protected]
        link
        fedilink
        01 month 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…

        • @[email protected]
          link
          fedilink
          0
          edit-2
          1 month 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”.