13 December 2008
Windows 7 does not cause interference
Posted by abe at 3:29 AM 0 comments
Labels:
04 September 2008
Produtc Planning for next Windows 7
Mike Angiulo’s post about Product Planning for Windows. Mike Angiulo is the team leader of the Windows PC Ecosystem and Planning team. It rather provides an insight in the workings of the product planning team which is working closely together with the Windows 7 feature teams basically making sure that Windows 7 will run on customer hardware and be sufficient for consumer, business and hardware manufacturer needs.
Creating an operating system like Windows 7 demands tradeoffs and Mike is mentioning three that the Product Planning team encountered recently:
First there is what I think of as the ‘taste test challenge.’ Over thirty years ago this meme was introduced in a famous war between two colas. Remember New Coke? It was the result of overemphasizing the very initial response to a product versus longer term customer satisfaction. We face this kind of challenge all the time with Windows – how do we balance the need for the product to be approachable with the need for the product to perform throughout its lifecycle? Do you want something that just boots as fast as it can or something that helps you get started? Of course we can take this to either extreme and you can say we have – we went from c:\ to Microsoft Bob in only a matter of a decade. Finding the balance between a product that is fresh and clean out of the box and continues to perform over time is a continual balance. We have ethnographers who gather research that in some cases starts even before the point of purchase and continues for months with periodic visits to learn how initial impressions morph into usage patterns over the entire lifecycle of our products.
Second we’re always looking out for missing the ‘trees for the forest.’ By this I mean finding the appropriate balance between aggregate and individual user data. A classic argument around PCs has always been that a limited subset of actions comprises a large percentage of the use case. The resulting argument is that a limited function device would be a simpler and more satisfying experience for a large percentage of customers! Of course this can be shown to be flawed in both the short term and the long term. Over the long term this ‘common use case’ has changed from typing & printing to consuming and burning CDs and gaming to browsing and will continue to evolve. Even in the short term we have studied the usage of thousands of machines (from users who opt-in of course) and know that while many of the common usage patterns are in fact common, that nearly every single machine we’ve ever studied had one or more unique applications in use that other machines didn’t share! This long tail phenomena is very important because if we designed for the “general case” we’d end up satisfying nobody. This tradeoff between choice and complexity is one that benefits directly from a rigorous approach to studying usage of both the collective and individual and not losing sight of either.
Third is all about timing. Timing is everything. We have an ongoing process for learning in a very dynamic market – one that is directly influenced by what we build. The ultimate goal is to deliver the ultimate in software & hardware experiences to customers – the right products at the right time. We’ve seen what happens if we wait too long to release software support for a new category (we should have done a better job with an earlier Bluetooth pairing standard experience) and what also happens when we ship software that the rest of the ecosystem isn’t ready for yet. This problem has the dimension of working to evangelize technologies that we know are coming, track competing standards, watch user scenarios evolve and try to coordinate our software support at the same time. To call it a moving target isn’t saying enough! It does though explain why we’re constantly taking feedback, even after any given version of Windows is done.
Posted by abe at 2:23 AM 0 comments
Labels:
29 May 2008
Why You Want To Book Your PDC2008 Ticket NOW...
If you're into any of the technologies that this blog covers, you'll be mad if you miss the Professional Developers Conference this year. It's actually been three years since our last PDC, so we're overdue! I'm really excited about all the things we're going to be covering at the PDC this year: those of you who have attended the conference in the past will know that we only run a PDC when there is major news to share, and we've got some killer content this year. Registration opened yesterday, so now is a good time to get ahead of the crowd.
We keep most of the session titles under wraps until the event starts - this is a future-orientated conference, after all. But even from the session abstracts we've posted so far, you'll see sessions that cover the Live Mesh, Internet Explorer 8, Windows 7 (including details on how to program for the multi-touch feature we showed off this week at Walt Mossberg's D conference), as well as really hardcore deep-dive sessions on topics like the internals of the Silverlight rendering pipeline and our internal usage of Team Foundation Server.
But there's one other thing that has me salivating about the PDC as a WPF developer. Jaime Rodriguez (content owner for the pre-conference) has secured none other than Charles Petzold to deliver a one-day session on WPF. Charles Petzold! If you've been living on Mars for the last twenty years, Charles is a titan of the Windows programming world, having written several seminal titles, including no less than two books on WPF. Indeed, Jeff Atwood describes him as "the guy who put the h in hWnd". Charles is a hero of mine - he writes concisely, precisely, knowledgeably and articulately. I remember bringing a stack of copies of his first WPF book to a team meeting; the product architects were as eager to read his verdict on their platform as a Broadway theater director is to see the early papers after opening night.
Charles isn't one of those speakers who seems to be permanently on the conference circuit - in fact it's pretty rare that you get the chance to see him "live" at all, even though he delivers some amazing lectures when he does present. This is a unique opportunity that you just don't want to miss if you're building your mastery of WPF. Here's what Charles wrote for the pre-conference abstract:
This session will go deep into WPF and explain the infrastructure and services that WPF introduces. Begin with a solid foundation in dependency properties. Advance to the retained-mode graphics system and visuals. Explore the layout model, routed input events, and data binding. Discover control customization with styling and templates. Finish the day with an array of powerful graphics facilities, including animation and 3D. After attending this code-heavy, few-slides session you will have all the great insights needed to develop responsive and dynamic WPF applications that are easy to build and maintain.
One day of Charles talking about WPF - that's worth the conference admission price alone!
Posted by abe at 5:13 PM 0 comments
Labels: