[{"_1":2,"_42":-5,"_43":-5},"loaderData",{"_3":4,"_10":11,"_40":-5,"_41":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9},"user","shoppingCartId","toast","locale","en","routes/_store+/_readers+/email_author.$slug/route",{"_12":13,"_39":-5},"book",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNjMxNzQ","title","Behind the PowerShell Pipeline","state","published","contactAuthorMethod","email","aboutText","

This book culminates almost 20 years of writing about and teaching PowerShell. In that time, I have come to realize that there is more to PowerShell than stringing some commands together in a pipeline or writing a PowerShell script. For years, I focused on the mechanics, such as how to write a script, use a cmdlet, and use the pipeline. But I have come to realize that there is more to PowerShell than just the mechanics. There is a philosophy behind PowerShell that is just as important as the mechanics. This book is about that philosophy.

These are my ideas based on years of teaching, presenting, and writing about PowerShell. These are ideas that aren't necessarily documented in Microsoft documentation. I like to think of these concepts as PowerShell's \"squishy\" bits. The parts that are hard to quantify but are just as important as the mechanics.

Learning the mechanics is easy. You can ask ChatGPT or CoPilot to write a command. But generally, you are writing commands for someone to run. Maybe you. Maybe the help desk. What do you need to know to create a PowerShell command that is fluid, easy to use, and easy to understand? What is the context in which someone will run your command? AI-generated code may be a good starting point but should not be the end. How can you create something that is as frictionless as possible for the user?

Is This Book for You?

The book's target audience is the PowerShell scripting IT Pro. A typical reader will have basic PowerShell experience and scripting skills. Ideally, the reader will have created scripts, functions, or modules and wants to know how to make them better and more user-friendly.

What Will You Learn?

While there is a lot of code in the book, that isn't the focus. You will learn how to think about your code from a user's perspective. You will learn how to think about your code from a greater context than simple execution. The code samples are there to illustrate the concepts and provide examples of what you can do to improve the quality of your code. I'll also share suggestions for making PowerShell easier for you to use on a daily basis.

Free Sample Chapter

The free sample includes sample chapters to give you a taste of what to expect. You are encouraged and more than welcome to download them. But why bother? Leanpub has a no-questions-asked refund policy, so it's completely risk-free.

Available Formats

Leanpub offers eBooks in multiple formats, and you get all of them with your purchase. I love the \"Send to Kindle\" feature. Note that the PDF is probably the \"highest fidelity\" version, especially in terms of code listings. Buy once, own forever.

","authors",[26],{"_14":27,"_28":29,"_5":30},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci82NjkzMg","name","Jeff Hicks",{"_31":32},"avatar",{"_33":34,"_35":36,"_37":38},"url","https://d308did4coypzi.cloudfront.net/avatars/949327/medium/jdh-oct2024.png?1738187803","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the author