Skip navigation.

Microsoft.com Redesign: GenesisAll recent postsHappy GIF Liberation Day!

Reality Check Ver 2.0

I think my beloved magazine, MSDN Magazine, is losing touch with reality. No, they've already lost it. For several years I've been drawing inspiration and great ideas from this publication, but their recent divergence to what's cool from what's practical is despicable. Nowadays the magazine is infested with trickery that has little place in the real world. Would you like to connect BizTalk with Office 2003 and, hey, let's have them communicate over SOAP via MSMQ! It's like a competition for some dubious award "The Smartest Pants In Town". What happened to the big names, like Jeff Prosise, Keith Brown, Fritz Onion, Dino Esposito, Morgan Skinner and others? These are people I've always been looking up to, and now they got caught up in the same frenzy.

Look at the topic lineup of MSDN Magazine 2004 (and these are taken from the covers. There's more inside each issue):

  • January - Longhorn, Indigo, Avalon, WinFS
  • February - Yukon
  • May - Visual Studio 2005
  • June - ASP.NET 2.0
  • July - Visual Studio 2005, SharePoint

Do you see the drift? The two missing from this list actually have some sanity instilled in them. It appears to me that everyone has become such as expert in .NET 1.1 and Visual Studio.NET 2003 that we can just move on to greener pastures. I have my SharpReader poll ASP.NET Forums during the day, and seeing the sheer volume of requests for help and questions over at the basic-of-basics forum, Web Forms, I believe we're not feeding beginners the right food. There were 64 or so posts today alone! Some of them went without an answer. Newsgroups receive even more traffic than this.

One may call me a slow adopter, an enemy of progressive thinking. Tell you what: ever since 1999 I've had every beta of every version of Windows, Visual Studio, .NET Framework installed. I kept installing, reinstalling, resolving conflicts, etc, for years. And I loved being in the front row. It was cool. While in Atlanta, I went to pretty much every Microsoft developer gig.

This time around I'm taking it easy. Maybe I've matured enough. Maybe it's because I have much more responsibility with my current job than at any previous jobs (which is, actually, true) and I get to be a "decision maker". Rushing headlong into a slue of betas and technology previews is not a task for someone who has a busy daily job and has people and objectives to answer for.

It's impossible for a person with any social life left to digest the avalanche of Indigos, Whitehorses and Longhorns storming into your line of work. If there was a clear source of information out there about these technologies I'd be content. But there's not. Right now it's jerking back and forth.

My point is this: the hype is reaching insane limits. With these technologies not even in sight it's a waste of time (your time) and money (your money). We've got real jobs, real projects, real paychecks. We've been, in essense, abandoned in favor of what's still amorphous. The "content strategists" at Microsoft had better understand this or Microsoft will end up with a confusion and morale problem down the road. We need help here and now. Having said this, I'm off to ASP.NET Forums to hang out with folks who are still stuck in reality.

Also, I'd like to make a promise to my readers: no Whidbey, Avalon, Indigo BS on this site until they are solid and become a good investment. I'm not here to waste your time. I want to help with what's important in our everyday lives as web developers.

Comments

Comment permalink 1 Xas |
I aggre with you.
I'm not a MSDN subscriber. I'm not a Beta eligible person.
I'm not a MS partner.
So I don't have Whidbey, Longhorn, NET 2.0 or anything else for the future.

Next year Longhorn will be shipped. And ? I will ask all my clients "please change all your systems, because I'm good on new tech, and MS will help me a lot if I got problems ?"

.NET is now too old to be more attractive.

Same scenario will appear when .NET 2.0 will be shipped. Everybody will do .NET 3.0...

Damn, I don't care Longhorn, I will go not before 2 years...

I want .NET 1.1 !!!
Comment permalink 2 Dave |
I completely agree. I would rather that the focus be upon the best practices for current technologies and how to correctly position your work for the upcoming tech.

Previews of Longhorn & Yukon are interesting, but the feature sets are going to change so much over the development period that previews are not much more than a curiosity.
Comment permalink 3 Gordon Weakliem |
I'm letting my MSDN mag subscription expire for the same reason. There are good, useful articles tucked in most issues, but I have enough problems getting what I have today to work.
Comment permalink 4 Stephan Troxler |
Wow - very nice spoken!
I agree 100% with you.
Comment permalink 5 Paolo Brizzolari |
I think that while I do agree with you that what we are working on now is still important and should obviously feature primarily, that it is also a good idea to keep up to date with the beta's and future technologies. I find that keeping the latest beta of .net on my machine allows me to spend a little time each day converting current apps and finding new features in the framework. In this way I keep ahead of the game in my company and I have a good idea of what I'm in for with regards to migration and new applications.

Emails and Notifications

Would you like to be notified when somebody responds to this post?  Would you like to have these comments emailed to you?

Submit your comment

Please enter only text since all HTML tags except hyperlinks will be stripped. Hyperlinks will become live links. Any comments with flaming or offensive language will be deleted. Be courteous to other posters. Thank you.

Your name (required):
Your email (optional):
Your site's URL (optional):
Enter this number
Type in the number above:
Comment (required):