The Human Side of PowerShell Scripting
summary
Claims that AI can generate syntax but not final design, then shows concrete fixes: use argument completer and ValidatePattern/ValidateScript to accept friendly drive letters and catch bad paths, add parameter aliases and parameter sets to accept Get-ADComputer output or CSV, emit rich custom objects with a unique type name and fields like percentTotal reportDate computerName, capture API responses via write-information stream and surface progress with write-verbose, plus ship a custom formatting file so the output is useful and debuggable.
AI-written summary · about
chapters (10)
- 0:00Human-centered PowerShell
- 1:55PowerShell beyond syntax
- 4:32Designing for real users
- 7:47Effortless command runs
- 12:45User input and validation
- 18:40Simplifying with aliases
- 25:51Meaningful execution feedback
- 35:13Rich output for downstream
- 43:01PowerShell tool principles
- 46:42Q&A
related talks
51mDon't do that, do this instead: PowerShell worst practices and..
46mFrom Script to Tool: Building Robust, Meaningful Tools with PowerShell
40mCode Writing Code, say what now! Meta Programming and PowerShell
37mUsing Windows PowerShell to create scripts your users want to use
47mTempting Fate: Patterns & practices for shareable scripts and functions
01h 45mWriting Award Winning PowerShell Functions and Script Modules
40mFrom Chaos to Clarity: Taming Data with PowerShell
35mImproving Your Attributes