I took a new job about a year ago, one that found me in a group of people who were struggling to do "simple" things, but doing them the "hard way". I came into this job, and because the core infrastructure is Windows Server, I learned PowerShell in about 6 months and started "solving" their problems by automating this and that. Things got easier, but the existing people thought me strange that I would resort to the "mere command line" for a solution rather than go about things using a GUI. My rule of thumb has always been "if I have to do it more than twice, script it."
These people have poo-pooed my every effort along the way and the boss has even called me out on it, despite me showing him that we are making strides where the team once did not. Sorry, I'm a command line guy at heart, and this will never change. I'm not a method man by any stretch. PowerShell is the orthodox way of handling Windows Server issues and that these people I work with don't want to embrace it is not going to slow me down.
We engage in useless meetings to have meetings. We talk about senseless things to jabber. I want to write scripts to automate certain tasks, but no. "What happens if you get hit by a bus, bro? No one knows how to code in PowerShell." My response to them was "I came here not knowing PowerShell, but I took the time to learn it and I'm productive in areas where you could be, too. I'll be happy to show you everything I've learned and coach you when you have time." They look at me like the proverbial deer in the headlights. I'm toying with leaving this year, as I want to work around like-minded, always-curious people, not people stuck in yesteryear.
Also if you are that much more effective you could start your own business, hire people and train them, then have 10x bigger margins then your old employer.
I have no idea what to do, what to offer, etc. It's funny, because when I'm at work, I don't really have to think too hard about solving a task. I'm generally the "smooth over" guy who fixes the things other people don't really see as issues, but having been in IT for so long, I can see the problems in the distance for a given job, as I've encountered them before. Most people just fly by the seat of their pants, but I love doing things once and well.
That, and I don't have the temperament to deal with the politics of the business side. I tried it, decades ago, and found it tiresome.
[I work in an educational organisation with around 1000 employees and around ten thousand students. There are something like 1 500 client PCs and the usual collection of servers. It is a microsoft shop. Powershell much in evidence.]
It's about building relationship and trust, and I feel it is less draconian as "kiss the ring".
I've made them look stupid by building something pretty good where they have been failing for 10 years with an entire team. Then I went and wrote another application in a strange new framework that had been invented in the past 15 years, and this startled and frightened them.
Don't be like me, kids. Play the political game. If you don't want your managers being told to dismantle the things you build, simply because you didn't kiss enough butt, learn how to raise your "EQ" and ensure the success of what you build. Otherwise, like me, you will have just written a bunch of stuff users loved, but management hated, and forced them to stop using.
It's too late for me; save yourselves.