Just about 4 weeks ago, I changed roles at Microsoft and joined the Technical Content team. I have to admit when I first learned of the opportunity, I was a little skeptical. I’m not much of a writer and I certainly didn’t want to become one. However, once I started learning more about the team and the opportunity, it was clearly the right fit.
Very few teams at Microsoft have the opportunity to directly impact how our customers and developers engage our products and services. Even fewer teams have the level of executive investment all the way up to Scott Guthrie; leading to change the way we think about technical content. It’s no longer about writers writing docs based on features in our products and services. Now it’s about content developers creating samples, tutorials, hands-on-labs, as well as writing docs that give our customers and developers the information they need to build solutions quickly and effectively. The focus is customers and developers – we want to understand what they need and provide it to them in the way they want it.
My team is responsible for developer focused technical content. That means we develop content for: Azure App Services, .NET/Core, ASP.NET/Core, Java, Node, PHP, Python, Ruby, Go, Visual Studio, VS Code, Visual C++, VSTS, and a handful of other tools and services – so, not much.
My hope is to use this blog to keep those who care informed regarding Microsoft’s investment in technical content as a way to help our developers and customers. From time to time, I’ll share some of our vision and roadmap as well as the cool updates we’re making to our technical content. In that spirit, here’s a few of the updates we’ve made in the last few weeks:
The .NET team shipped the .NET Glossary which is a huge step to providing users that are new to .NET a quick reference to understand frequently used terms and acronyms within the documentation. It was a big effort involving multiple groups to pull it off. My understanding is Scott Hanselman has a blog coming. That’ll be cool to see.
Last week, we released two new dev centers focused on .NET and Node. Our goal was to get folks up in minutes on Azure and have a left to right view for the community. We also wanted to have a homebase for advocates and the communities we are connected to via advocacy. More recently, we made similar updates to the Java Developer Center; focusing customers on our quickstarts, tutorials, and samples. These are definitely big steps forward for OSS on Azure.
I’d love to hear feedback as I continue to share. Let me know what you think about what we’re doing.