The games have come and gone. Microsoft's 2011 Scripting Games were something I had been looking forward to as long as I had been dabbling with PowerShell. I am very much still a beginner, based on my experience and the judging and feedback I received on my scripts this year (more on this later). I didn't go into the games with the intention of winning, but just completing all 10 events. I really wanted to get feedback from the MVP judges, to learn both PowerShell and best practices.
The games shed light on my shortcomings in regards to PowerShell, and also a little insight into me and my inability to focus and read all the directions on a few of the events. I learned quite a bit, from the very first script to the very end. So it was bitter sweet for me. Bitter because the two scripts I submitted that according to the judges didn't work (only a single star indicating submission), I wished I had done better, though I'm certain the scripts returned the required information, the output or the effort I put forth getting the required information left something to be desired from the judges. Poor assumptions on my part.
My experience with PowerShell up until this point had always been - Task - Script - Test - Execute. Quick, Dirty, Learn what you need to, move on. Getting the job done, quickly and safely (read -whatif) but this simply didn't cut it in the 2011 Scripting Games. Holy mother of god, some of the scripts in the "beginner" class left me in awe.
The sweet -- I finished all 10 events. I had A LOT of fun. I learned quite a bit, the games exposed me to a lot of new things. Another great thing about the games, it introduced me to a whole lot of people. Following #2011SG on Twitter, most who had Twitter, who were in the games, were posting. Many opportunities popped up to offer advice, get advice, which led to discussions and quick lessons offline about PowerShell. This allowed me to get some tips/how-to's from those with more experience than me. Hopefully creating some friendships going forward.
When I get the opportunity to visit the Judge's entries/answers for each event, I'm certain I'll learn even more. Quite simply there is a crazy amount of information to take in, almost impossible to take it all in at once!
My goal over the next two weeks is to take each event, the judge's comments/feedback and what I learned and apply them to each script. Improving them in an attempt to better myself and gain more exposure to PowerShell. Do I win anything? Nope? Will anyone judge these? Not officially. But it's for my own self improvement, nothing more. Am I expecting "five stars" in my second attempt. Nope. Quite honestly, there is a lot of room for improvement in my scripts, and that's what I intend to do.
I already can't wait until next year's games. And the 2011 games just ended. It'll be a long year! But I've got a lot to learn, a few books to read and plenty of time to get ready for the 2012 Scripting Games.
To the Judges who took time out of their personal lives/jobs, thank you. The games would not have been what they were without you. To Ed Wilson (The Scripting Guy) for being The Scripting Guy. To Jonathan Angliss, @j_angliss, thank you very much for your time spent offline giving me PowerShell tips. As I said before, if I'm ever in TX, beer's on me. Jonathan Tyler, @jonhtyler, your blog post on PowerShell output shed light on something that I hadn't really known or thought about, putting PowerShell output into prospective. Thank you. Steven Murawski, @StevenMurawski, I believe I may be the topic of a couple of your recent blog posts. I'm glad I could contribute to a great resource, and thank you for taking time time off line to offer assistance when I had questions. To Joel Bennett, @Jaykul, for all your help on #Home, the assistance/guidance is much appreciated. Anyone else I forgot, and everyone else on #Home, thank you!