The Ozzie Effect? -- Visual Studio Magazine

Desmond File

The Ozzie Effect?

Michael Desmond, founding editor of Redmond Developer News and Desmond File blogger, is on vacation. Filling in for him this week is John Waters, contributing editor of RDN.

All this openness at Microsoft is coming just as Microsoft Chairman Bill Gates goes into semi-retirement, so it's probably worth giving props to new Chief Software Architect Ray Ozzie for what promises to be a smart move for the company, long-term. Ozzie was reportedly the force behind a 2006 open source project to create a translation bridge between Microsoft OOXML and the ODF standard.

Back then, we saw the translator initiative as an early example of "the Ozzie effect." He lacks his predecessor's love of the spotlight, but Mr. Ozzie's influence on the company in an increasingly open and less Microsoft-centric world bodes well. --John Waters

Posted on 02/28/2008

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.