Why I use PowerShell
PowerShell is useful to me because it turns a repetitive task into a script that I can run easily and consistently. I use it for troubleshooting, administration, and small automations.
How I approach a script
- Work out what I want the command to change.
- Test the command on a limited scope first.
- Add basic error handling or checks where needed.
- For scripts that alter multiple systems, I prefer a preview or validation step when possible.
- Make the output understandable enough to troubleshoot later.
- Document required dependencies, required permissions, and changes made by the script.
What I’ve been learning
I’m working on improving how I structure scripts rather than keeping everything as one-off terminal commands. That includes reusable functions, parameter handling, clearer output, and better documentation.
Real-world example
As part of my duties as a technician for Contra Costa Health, I developed a PowerShell deployment to install Webex silently and machine-wide across a fleet of healthcare translator workstations to support the department’s transition to VoIP. I had to get familiar with installer switches like ALLUSERS and SILENT and integrate them into a script that remotely connects to each machine. The script can digest a .CSV list of computer names or IP addresses and loop through it, remotely installing Webex on each device without interrupting the users.