header image

Is PowerShell too big?

Posted by: | July 30, 2013 | 1 Comment |

I was thinking the other day about the differences between PowerShell v1 and the new v4 we’ll be getting soon. There is so much in PowerShell that its very difficult to be an expert in aspects.

Think about these topics for a moment:

  • PowerShell pipeline
  • Error handling and debugging
  • Objects
  • Scope
  • Formatting
  • Extensible type System
  • PowerShell remoting
  • PowerShell jobs
  • Advanced functions
  • Modules
  • Splatting
  • CIM sessions
  • Workflows
  • Scheduled jobs
  • Internationalization
  • Desired State Configuration

And all of that is before you start adding in the cmdlets for administering specific parts of your environment – AD, Exchange, SQL Server, SharePoint, DNS, DHCP, networks, backup etc etc etc.

PowerShell has got to the point where you can’t expect to be an expert in every facet. Have a working knowledge of as much as possible but specialise where it will help you do your job.

That’s why it took three of us to write PowerShell in Depth!

under: PowerShell original

1 Comment

  1. By: Jan on July 30, 2013 at 3:29 pm      

    Well said!
    I see the challenge on a daily basis, where i am the only one of 15 persons in our IT department who actually is having some knowledge towards PowerShell, my colleagues ask me to PowerShell this and that, forcing me to expand my insight in PS in corners where i normally don’t come around. Never worked with VMWare, SQL, Oracle, Sharepoint and HyperV before, but because i preached to my Co-workers about all the good stuff PS can do, I have ended up doing stuff which take some time to learn and taking away focus on my core business which is administering AD, Exchange and Lync with PowerShell.

    I shouldn’t complain though, my colleagues is slowly opening the eyes and realize that PS is something they need to master as well.