I have been asked recently by “Pack Publishing” to write a review on their latest PowerShell book called PowerShell troubleshooting guide written by Michael Shepard.
I have read the book in the electronic format, so i cannot comment on the size, global aspect and other physical information that is related to the print copy. I can (and will) talk about it’s content.
I almost buy every PowerShell book that get’s out. I like to be up to date with my knowledge, and try to know the latest of the latest before everybody else. A lot of the books I have read before (the “best sellers”?) are very often written by the same authors. Having the opportunity to read this book from Michael Shepard (Which I didn’t know until then) is also another very important point for me. It gave me some ‘fresh air’ and another author to read and learn from (when they are not french or German).
The book is composed of 8 chapters for a total of 195 pages. If you compare this book to other ones focusing on the powershell topic, it is fairly small book. The text is easy to read and the powershell examples are clear and easily understandable.
Most of the examples are based on real life scripts from Michael shepard and can easily be re-used in your own scripts (such as Test-TCPConnection). The only little thing is how some of the script examples get sliced and spread over on 2 pages. This is of course not a big deal, and most likely only a personal preference.
About the author:
Michael Shepard has been working with computers since the early ’80s, starting
with an Apple II in school and a Commodore 64 at home. He started working in the
IT industry in 1989 and has been working full-time since 1997. He has been working for Jack Henry & Associates, Inc. since 2000. He has had various roles in that same company, but Michael started his career as a Database programmer. Michael also blogs on thepowershellstation.com, so don’t miss it.
For many of us, we just came into powershell just by luck, or the door was open, pushed, forced, wanted to, needed to, evolved from VBS etc… A lot of different reasons could have pushed us here, but the most of us are system engineers, or system admins. Even though we have been learning some development at school, some of us just didn’t use it anymore. PowerShell was actually a great way to get (a little) back to it.
System engineers are not developers actually, scripters are also not developers. There is some knowledge that we do not necessarily have, that developers have. Things on how to work efficiently with code, how to make it resilient. How to back it up. How to work with several persons on the same code etc…
This is what in my opinion makes a big deal, Michael has this developer experience, and bring it to us in a way that after reading this book, we will not simply write smart scripts, but also organize our code smartly. And that, for me, is was very valuable.
When I actually got asked to read this book, I thought to my “What more to learn in troubleshooting Powershell scripts than the regular technics such as break points, try catches etc..?”. Actually, a lot!