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.
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.
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…
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)
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.
oh no…
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.
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…
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”.
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)