I want to try something new, and I expect it will take more than one article, which is why this is titled Part 1. Last week I introduced you to creating PowerShell tools using the Crescendo module. My goal was to provide enough background and information for you to get started. There’s more detail I can cover, and I decided the best way would be to build a Crescendo-based tool from scratch.

Usually, my articles are carefully laid out, and all my sample code is prepared ahead of time. Today, I want to try the equivalent of a live coding session. I have very little prepared other than a general direction I want to go. I want to build a Crescendo module around a command line tool I use all the time. As I write my code, mistakes and all, I will write about it here. I know I won’t get everything completed in a single article. You are welcome and encouraged to follow along. I’ll be building my module in PowerShell 7 since that is a requirement for Crescendo. You may not have a need for my finished product, but the development process is the takeaway.

I’m trusting that there is value in watching how I work. I’m not implying that my development process is the best or only way to write PowerShell code. But I think it is helpful to see how other people code. I’ve learned a few things over the year by looking at other people’s code and I hope you’ll pick up a thing or two from watching my process.

Github CLI