Microsoft Big Brains: Brad Lovering
![mary-jo-foley](https://www.zdnet.com/a/img/resize/e044720b80efb53e29d54a7b9c817e3e57f3f2b6/2022/08/05/8215236b-63b7-491f-91ad-190439d0bf94/mary-jo-foley.jpg?auto=webp&fit=crop&frame=1&height=192&width=192)
Just before retiring from day-to-day responsibilities at Microsoft, Chairman Bill Gates said that he expected Microsoft's 22 Technical Fellows to get a lot more publicly visible -- now that they wouldn't be living in his shadow. While some of the Microsoft fellows already have been active on the public-speaking circuit, many of them are not widely known outside the company.
I've launched this series -- "Microsoft Big Brains" -- to help remedy that shortcoming. In the coming weeks, I am hoping to profile as many of the company's tech fellows as to whom I can get access.
Microsoft's Technical Fellows came to the company via a variety of different routes. Some of them run divisions inside the company; some focus on particularly thorny technical issues that may span a variety of product units. Regardless of where they sit in the organization, the fellows all have been charged with helping Microsoft craft its next-gen products and strategies, much the way that Gates used his regular "Think Weeks" to prioritize what Microsoft needed to do next.
Every three to four years during his 20-year career at Microsoft, Technical Fellow Brad Lovering has had a fireside chat with Chairman Bill Gates, CEO Steve Ballmer and Senior Vice President/Chief Technology Officer David Vaskevitch.
"It's a balance. I say what I'm interested in. They talk about getting the right teams and assembling the right pieces," Lovering says. And then Lovering goes off and works on whatever developer-focused project that he's interested in and needs him most.
It was four years ago when Lovering initially took on the assignment of working with Microsoft's then-fledgling Oslo modeling tools and strategy team.
"The first year was a lot of customer stuff. Then it was a year of getting the team in place. There were various incubations in various places," he reminisces. "It will be five years total by the time (Version 1) ships" as part of Visual Studio 2010.
It's somewhat atypical for Lovering to be managing a team of a couple hundred people, as he is doing now.
"I spend most of my time on tech design," he says. "Half my job is typically talking to internal (Microsoft) partners. Now (with Oslo), we're also starting to talk to external partners" he says.
"I'm staying with the Oslo team through RTM and hopefully for another turn for Version 2. I'm excited to do a Version 2 for the first time," says the typically on-to-the-next-thing Lovering.
What's left to do after the first set of Oslo deliverables (a shared repository, the M modeling language and the Quadrant visual-modeling tool) are completed? Lovering says there is a never-ending laundry list, especially around the cloud. Already, the Oslo team has started working with the Azure (Red Dog) cloud OS team to build a domain-specific language (DSL) using Oslo.
"You need a model-driven approach for these big systems," like Azure, Lovering says
There are potential synergies between Oslo and the System Center systems-management tools and technologies, the Dublin application server team, the Dynamics CRM and ERP wares, too, he says. Almost every big software-development project at Microsoft could benefit from Oslo, Lovering says. Meanwhile, don't be surprised to see many next-gen Microsoft tools and products include Oslo integration as a feature. Visio, for example, could benefit from tighter import/export integration with Quadrant, Lovering says.
"I spend so much of Microsoft's money doing crazy stuff," Lovering concludes. "But they keep saying, 'go,go, go.'"
So off goes Mr. Oslo to help build out more domains and find ways to get developers on board with Microsoft's modeling technologies.
For all of the “Microsoft Big Brains” profiles, check out the Big Brains page.