With PowerShell finally going cross-platform with Windows 8 I keep hearing the same comments over and over – “just write a script for that”
You know what? Not everything needs a script. A few commands maybe, but not a script.
Why do I bring this up? Because script writing is intimidating. You have to understand loops, arrays, object types, schemas, properties, and other developer-type things.
But if you only have a make a couple modifications to settings, every so often or discover something. You don’t need a script for that, you need some commands.
And this is where the lingo and the action are becoming disconnected.
If you look at it one way, PowerShell is to Windows what BASH is to Linux and what Command was to DOS. A way to get things done. A place to find things and do things.
Did everything that you did in DOS have to turn into a BATCH script? No. But back in the day we did write some pretty complex user logon and logoff scripts. Why?
Because certain tasks needed to be repeated over and over. That is where we need a script over a few captured commands.
My other big gripe is script or command examples. Folks that blog some long and highly complex one-liner that is very difficult to comprehend because you get lost in the pipeline. The big disservice being that they never do it long hand.
Most folks that I encounter these days are either at the 100 level of using PowerShell or at the 300 – 400 level. You just straight through the 200 level when you write a script or suddenly grok objects.