Yeah, here's the thing about being complacent.
If it ain't broke, don't fix it. Software isn't always better because it's new. Procedures either. I'm not about to have anybody use Ruby, just because some 20-something new hire things it's cool. And while I like Agile, I know that it works only because the team meets every day, forces them to track real progress vs estimates, measures what's happening in real time and basically keeps their eye on the ball. Stuff I was doing about a decade before the word, "agile" existed.
So, color me unimpressed by Powershell, Agile, objective C, json and Azure. These technologies are neat and sometimes useful, but ONLY if they solve a problem and/or IMPROVE something - a test many new technologies fail, pathetically (e.g. 100 lines of powershell to do what one line of "NET USE xxxx" does).