Tim Long

Back in the day, a beta was a piece of pre-release software that knowledgeable users – like developers and IT professionals - could try out and help find the bugs and usability problems. It was about engaging the customer in the development process. I took part in the beta programmes for Windows 95 and MSN and Microsoft was willing to compensate people for help finding their bugs in those days. For my efforts, I received a complimentary copy of Windows 95. For helping to test MSN, I received a free gift (I think it was a T-shirt and a nice quality one at that). During the testing of "Chicago", I received new builds of Windows 95 and the Plus pack on CD-ROM every few weeks and slowly built up a whole drawer full of beta release CDs (internet access was limited to the elite few in those days so downloading was simply not an option). At the time I was a software engineer in the telecoms industry but not in any way affiliated with Microsoft - I was just an ordinary guy, an end user and software developer who showed interest in helping to debug the software. I really felt involved in the process. I felt like I was making a genuine contribution and I felt like Microsoft valued my enthusiasm.

Now let’s draw comparisons with the situation today. The 2007 Office System beta 2 was released two days ago. Anyone can download it for free in a few hours. I can get a copy by mail but I have to pay for shipping. I am a registered Microsoft partner and I am getting this beta at the same time as my customers, the same time as, basically, the rest of the world. The beta is not officially supported (how could it be?) and if I find a bug (which I have already) then it is really not obvious how I am supposed to feed the information back to Microsoft, if it is even possible. There were earlier beta releases but I would have had to jump through hoops to get involved in those. I tried, but being a developer doesn't cut the mustard when it comes to helping Microsoft debug its software. It seems like I’m supposed to feel privileged to have been allowed access to this beta release. I feel like Huckleberry Fin tricked into painting Tom Sawyer’s fence. It was simply too important a task for me to be allowed to do it.

Microsoft has made a marketing art form out of pre-release software. They have turned it into a big fat carrot that they can dangle, a political tool to appease the members of their partner programme. I understand that Microsoft needs to limit involvement in early beta testing programmes, but they have made a rod for their own back. Beta software is no longer about developers trying to debug. It is all about marketing. Beta releases have been turned into a feeding frenzy of any old Tom, *** and Harry just trying to get a sneak peek at the new software. Organisations such as Culminis clamour to provide the illusion of membership benefits by announcing a “special” URL that gives you nothing extra but helps them justify their own existence. Partners wield beta participation like status symbols and use it as a marketing tool to differentiate themselves from lesser partners who were too humble to qualify.

I think Microsoft has lost its way in how it engages with its partners and the developer community. Widespread public availability of pre-release software has diluted the meaning of what a beta release was supposed to be. Newsflash – a beta release was not supposed to be a marketing tool. It is supposed to be about developers and IT professionals finding and fixing bugs. Remember your developers and partners, Microsoft. I’m sick of  jumping through hoops trying to help you. I’m sick of getting access to pre-release stuff the same day as my customers. I’m sick of getting access to politically motivated beta releases the day before the product “goes gold”. That behaviour does not appease me; it is an empty meaningless political gesture. Let's get back to what beta testing is meant to be - developers and IT professionals helping to shape the future of software.

[Update: this post generated a discussion thread over here]

Windows PowerShell RC1 has been released and I think the heralds is sea-change in the way scripting is done. This new shell, codename Monad, has one important difference from previous command shells – it does not use text as the fundamental data type. Whereas almost all previous command shells operate fundamentally on text, Windows PowerShell operates natively on .NET objects. So when you pipe a series of commands together, you’re not passing text along that pipe but objects. This should make utilities like sed and awk unnecessary as that sort of processing can now be done in .NET objects. The power of this new paradigm is only just starting to become apparent and I’m sure we’ll see lots of interesting uses emerging.

The command language borrows from VAX/VMS, Unix and DOS so for example options are specified unix style (command –option). I think this new technology is ultimately going to eliminate the need for things like VBScript and JavaScript, because if you need new functionality you will simply write a new Commandlet in VB.NET, or any .NET language, giving you all the power of Visual Studio. Time will tell, but I think the writing is on the wall for traditional scripting. Anyway, check it out for yourself. The Windows PowerShell home page has the latest downloads and some webcasts with background information.

www.microsoft.com/powershell