I meant to post this earlier but life just got ahead of me.  Anyway, I’d like to announce that I’m now co-hosting the PowerScripting podcast with Jonathan Walz.  Our show, now in episode 8, is the only podcast dedicated to discussion about Microsoft’s PowerShell scripting language.  Jonathan and I recorded our first joint show the weekend before last, and the podcast was released this past Tuesday.

It’s actually funny how we met.  I had just found and started listening to the podcast when I heard Jonathan say something about the Atlanta weather.  I sent him an email right then asking him where did he really live as Atlanta has a huge footprint.  I was sure he’d be on the other side of the city from me, 50 miles away or somesuch.  After all, what are the odds of me finding a random guy online who happens to live close by?  (Er, not that I go trolling for guys online.)  Well it turned out that Jonathan in fact lives in the same suburb of Atlanta as I do, and he lives at most about three miles away!  Talk about small world.

Anyway, I hope to be able to contribute to the show and help make it better.

About the show:

The PowerScripting podcast features the following:

• Discussion of PowerShell-related news items
• Segments on problem-solving and “gotchas” we’ve encountered.  We go through the fixes too, so hopefully you’ll not make the same mistakes. 
• A Cmdlet-of-the-Week segment, where we start basic (reading an extract from the help file), then dig deeper into some examples where the cmdlet may come in handy.  Code samples will be referenced in the show notes.
• Interviews!  We haven’t done any yet, but this is in the works–stay tuned for that.
• Resources for the new scripter and the pros alike.  We’ll be sure to include evaluations of commercial products as well as pointers to the best freeware out there.  We’ll also share with you the best blogs, books, and other cool stuff.
• We scour the net for the best PowerShell tips too.  We’ll break them down into easy-to-digest chunks so you can get the most out of it.  We’ll also get into conceptual stuff that may be light on code but heavy on process, workflow, and best practices.
• Last but not least, sometimes you need a big complex script to solve a problem, but sometimes your work can be simplified with a single one-liner.  When you can fit everything that needs doing in one line, you know you’ve got a keeper.