The concept behind Beginning PowerShell for SharePoint 2013 is an idea I’ve been holding on to for a few years now. In every technology stream you look at, there’s always a clear distinction between administrators, referred to as IT Pros in the Microsoft world, and developers. Administrators often think of developers as taking too many risks and not considering the overall impact that their solutions may have on the system as a whole. They also don’t like the fact that they don’t have control over what is being executed by the code provided. I can’t tell you how often I’ve seen developers provide administrators with command line executables for them to run on SharePoint servers in order to fix some issues with the SharePoint farm. On the other end, developers tend to think of administrators as being too restrictive and always trying to put sticks in their wheels. I’ve seen this everywhere I’ve worked in the past, and I’m sure most readers can picture themselves in this situation.