[youareterrible]

This thread is full of people who are bad at PowerShell complaining about not using PowerShell properly.

Learning it is one of the most important things a Windows sysadmim should do, today. Hell, if you consider yourself a Windows power user, you should learn it.

A single sub-1000-line script I wrote in a couple days of downtime has saved over $10,000,000 in taxpayer dollars and has never stopped working since the day it added itself as a scheduled task. I am not a programmer.

It's very powerful and generally limited only by your knowledge of how to do it with PowerShell. And all you need to start and learn everything are two commands. Three if you count update-help.

Get-help Get-command

[telltruth]

If you were writing bank app in COBOL on mainframe 24X7 for many decades, you would have probably found it intuitive, productive and high value as well. The problem is that for most people scripting is not their day to day job. It's something you do for may be a day after you write month worth of code. If your scripting language is ugly and unfriendly you will tend to forget it and basically have to re-learn it every time you try to use it. That's not a good or productive experience for people who are writing 10 lines of script after long intervals.