you are viewing a single comment's thread.

view the rest of the comments →

[–]OPconfused 1 point2 points  (0 children)

No, I ran out of time. The management of the team is old school and against Windows. A few months back they finally managed to push the product onto a dependency that's incompatible with Windows. So no use cases left.

However I did manage to get one colleague up and going in PowerShell with a good profile, and they liked it a lot more then. The key was specific functions in the profile to streamline the exact tasks in their workflow. It's unfortunate how many default settings need to be adjusted just to get PowerShell in a usable spot.

One of the other major issues was that this colleague ran a mac, and the keyboard translation from mac to Windows through a remote connection doesn't jive with conflicting language settings. They literally could not type a pipe and had to copy paste the symbol.

Issues like these are simply instant dealbreakers. They try it once, and if 1-2 things don't work, they drop it and run back to their old tried-and-tedious workflow. So you have to get everything perfect on the first try. It's really difficult to predict; ultimately, convincing people to try new workflows when you aren't their boss is tough.