From Learn PowerShell Scripting in a Month of Lunches by Don Jones and Jeffery Hicks

This article is about learning to draw the line between two equally important kinds of script – tools and controllers. Specific techniques are suitable for tools, and different ones are suitable for controllers. Each set of techniques is designed to reduce your workload, debugging, maintenance, and increase readability and reusability. Knowing which kind of script that you’re writing helps direct you to the right set of techniques, and this is the key to being a successful scripter and toolmaker!

From Learn PowerShell Scripting in a Month of Lunches by Don Jones and Jeffery Hicks

Before you sit down and start coding up a function or a class, you need to do some thinking about its design. We frequently see toolmaking newcomers charge into their code, and before long they’ve made some monstrosity which is harder to work with than it should be. In this article we’re going to lay out some of the core PowerShell tool design principles, and help you stay on the path of Toolmaking Righteousness. We’ll include some concrete examples.

From Learn PowerShell Scripting in a Month of Lunches by Don Jones and Jeffery Hicks

We see a lot of people jump into PowerShell scripting much the same way they’d jump into batch files, VBScript, or Python. Nothing wrong with that – PowerShell is able to accommodate a lot of different styles and approaches, but you end up working harder than necessary unless you take a minute to understand how PowerShell really wants to work. We believe that toolmaking is the real way to use PowerShell.