Ask not what Microsoft can do for you but what you can do for Microsoft. That's really the inspiring quote that President of the new colonization group - aka Windows - needs to say to the unwashed masses of tomorrow.
Microsoft is taking on a mission that looks to go beyond the moon, they want to land on Jupiter and it will be done with Apollo. Still confused?
If you've not paid attention to all the codenames flying about the place you'd be forgiven to be confused as there's a space theme happening and with these code names its quite interesting to see how the objectives for the next generation of Microsoft is likely to shape up.
Jupiter is rumored to be the reset button to Windows Presentation Foundation (WPF) and Silverlight. A reset is the latest suspicion as just yesterday I found out that the XAML ethos within Microsoft has been disbanded and set to various corners of the company. Some went to Internet Explorer team, some went to Windows teams and others went to Google, Amazon and Facebook.
Why disband the teams? It is time for pencils down folks, let us stop piling on code for the existing stuff but now let us set our sights for the future, let's be bold. Let us be daring. Why land on the moon when you can land on Jupiter floating on a cloud of Azure? (Ok, I lost myself in that metaphor as well).
Ok fine, I have gone through the seven stages of Silverlight/WPF grief and I am at acceptance I think.
In order to better prepare for the mission ahead, let us think about the various things we need to account for prior to launch (September).
Replace Crew Members.
Inside Microsoft there is a lot of toxic turmoil going due to internal re-orgs (which is fairly common) that fueled with how the Global Financial Crisis has affected employees etc. it's no secret that Microsoft are losing some quite influential and dare I say, hard to replace staff to places like Google, Facebook, Amazon and so on. I personally know of three employees who have hated working for Microsoft for quite some time but have been stuck due to housing prices in Redmond etc not being ready enough for a resale - that is - until Google, Adobe, Facebook and soon Amazon have campuses of their own in Seattle.
Now the super geeks have alternative employment options. Microsoft is now on notice, treat me better or I will leave. The later choice has been winning in my opinion and the more the new found employees have sent me messages of "Omg, its way better over here than Microsoft" which has to be salt in some current employee's wounds whom are likely staring down the barrel of uncertainty in the company given its end of year commitment scoring mixed with the demise of what we used to call the Silverlight/WPF & Blend ethos. What to do!.
A gentleman and fellow .NET scholar Jose has done the best he could in reverse engineering Direct UI (rumored to be the leaked incarnation of Jupiter). He has some insights that are both great and disappointing at the same time. The great part is it could very well be the next iteration of what has to come in the landscape of C# and XAML for tomorrow's UX Pioneers.
The downside is its 3-5 or maybe more steps backwards in the current feature parity you have all eagerly waited for over the past 4 years. There are some fundamentals in the room whilst there are concerns around some of the other features that may or may not make the cut for version one.
If I know Microsoft and I like to think I do, this is likely to be yet another one of those traditional "version 1" moments whereby the team(s) behind the product eventually stumble across the finish line, exhausted but barely breathing enough to shout "Give me feedback on what you want in version 2, it will be better I promise" followed by some metaphor about how it's a marathon and not sprint to the finish line (We got great mileage out of that with Silverlight and I dare say you could get a few more products out of it yet).
The tooling is likely to be not in place during this version 1 lifecycle as my sources tell me that the Blend Team aren't cranking out the vNext improved world of Microsoft. I know Steve Sinofsky has had a few ambitions about what the Tooling should look like in the perfect world of Windows vNext frontier and I am guessing he did not play well with others in the Devdiv team(s) to share such ambitions.
That being said, either there is a skunk works tooling team hidden in some random building in Microsoft that others do not know about or the tooling story behind this next frontier is unlikely to be in place before Sept or for whenever this next version of our beloved Silverlight/WPF ethos occurs.
What I mean to say is welcome all to Microsoft 2005. Hold onto your Winforms or ASP.NET MVC for a little bit longer and for those of you in Silverlight/WPF investment land(s) - try to not focus on the future but the now (best to keep your code base as lean as possible and not to tightly wound in client-side logic).
Put vital organs into Escrow.
Microsoft are quick to throw technology at a problem first and then ponder as to why the problem existed. I've often personally seen strategies - wait, that's not correct, strategy requires forward thinking - tactical decisions (better) made around trying to grow developer audiences.
The assumption are
"ok, we're not making our tech palatable enough, lets steal stuff from Ruby On Rails, Apple or Oracle to make it better".
The absolute harsh reality is often a lot of non-Microsoft customer(s) etc. just don't like Microsoft (Ever liked a girl/guy and they don't like you back? You try changing your clothes, hair, car etc. and still nothing. Welcome to the Microsoft Developer outreach program, you will fit right in).
The other side of this coin I guess is those of you who adore Microsoft for what they are. You spend thousands of your own dollars to go to various events to listen to Microsoft confuse the absolute crap out of you. The problem is lately, they seem to be a company you just cannot bet on for the future.
Grandiose plans to land on Jupiter may be bold, daring and exciting but is it dependable? Can this company commit to a master plan and is this a plan or just a tactical political brain dump mixed with a lot of Microsoft experimentation.
Is it a case now of not waiting for the next Service Pack but now waiting to see if a product can get past version 3 and 5 before you really consider it as a viable option of the future?
In order to prepare for this next mission, someone has to donate some good will to the fans of Microsoft technology. That means you cannot stick to the ye olde "need to know information" mentality. You got to bring your roadmap(s) for the future and you got to show us that you're telling the truth that you want to aim for Jupiter and not some closer planet or worse - the unknown void beyond Jupiter.
Commit and stop being assclowns.
Commit to us so that we may commit to you. No more lies, No more "I've got a secret, can you guess!" and lastly no more internal political child play spilling over and into the blogosphere. It's time to be a big boy company and use big boy strategies with big boy plans mixed with a lot of big girl personality (somehow that did the ladies no favors).
If we are to take on this mission, it's time for a smarter playbook around transparency and if Steve Sinofsky is willing to bring the "come to Jesus" moment for the company around consolidating the entire product lines into a consistent continuous experience across all devices with a developer/designer experience to boot. Great, I personally will print out a t-shirt that says "I'm back in team Steve" (heh my old team inside Microsoft was called Team Steve...Steve the manager though was a arrogant jerk, different story, different time).
Right now its just a case of me holding up a really sick puppy that others have kicked and telling you all about the neglect its owners have given it. (If I quote that metaphor I was given last night by a friend).