Our small software shop has made its name by aggesively adopting new technologies. At different times it's been Pascal as a business apps language (we've been in the market for a long time... :-( ), LANs, PowerBuilder, Lotus Notes, Java, .NET. Along the years, we've been among the first in our country to create business apps using these technologies, often with Beta versions. Now is the time for .NET 2.0, VS 2005 and SQL Server 2005: we are currently working in 3 projects with these new technologies (it would've been 4, but the 4th was a big bank and they dimmed too risky to use 2005, so we settled on .NET 1.1 and VS 2003). About our 3 Whidbey projects:
- The first one is a new product created in-house so any delay in the appearance of VS 2005 may impact our budget but otherwise we can pretty much handle it.
- The second one is a joint migration from .NET 1.1 with an old friend and customer. as his target market is small financial institutions (tiny, from the US perspective) I'm confident we can go ahead with the Beta 2 Go Live license. Still, delays in Beta 2 or significant changes in further stages will be harder to handle.
- The last one is a web site for a big local company (small from a US perspective), this is the one that has me worried as any delays in the roadmap will get the customer very nervous and impact the project.
That is why reading Shaykatc's blog has been reassuring: every time MS insiders start to talk about their bug fixing process, it means they are seeing the end of the tunnel really close, this particular tunnel being Beta 2. And of course I would like to hear stories of any other dare devils of commercial Beta development!