Where's Waldo? -- Visual Studio Magazine

Desmond File

Where's Waldo?

Or, more precisely, where in the world is Ray Ozzie? Outside of an appearance at the Web-centric Mix07 developer event in Las Vegas this April, Microsoft's chief software architect and presumed successor to Bill Gates hasn't been featured at any of Microsoft's major conferences.

We're reading tea leaves here, but it seems that much of the early light and heat of Ozzie's arrival in Redmond has burned off. Meanwhile, CEO Steve Ballmer is taking center stage at key events like Microsoft's Worldwide Partner Conference, going on now in Denver.

Could it be that Ozzie's vision for Microsoft, one founded on the openness and innovation implied by Live Clipboard and similar projects, has bogged down?

Tell us what you think. E-mail me at mdesmond@reddevnews.com.

Posted by Michael Desmond on 07/11/2007

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.