![]() Think about, for example, what we download on-stage in terms of mobile development. ![]() That is actually one of the biggest powers of the IDE. The power of the IDE is that there’s a whole set of – it’s particularly powerful when you have very complex multi-step processes that will just simplify and automate it for you. You can say they’re all for editing words, but I use them and a lot of different people use them for different scenarios. And I’m not really confused about when I’m gonna use each one. “Do you use Notepad?”, I again get a nod. When you start talking to a lot of developers - a lot of different needs… And I always ask people, like “Do you use Microsoft Word?” Usually I get a nod. Yeah, so first of all, why we started to do that is that we realized that there are different types of developers. And then with that, not to mention we also started to develop Visual Studio Code. That capability of us understanding developers’ needs and open sourcing our core framework capability, and really allow this breadth that has been super powerful for us. This is when we started doing iOS and Android development, helping with the mobile side, and we look at what people really need in the cloud space, in the mobile space, and we take cross-platform, and it’s become a fantastic way for our customers to share code, between their Unity gaming, to their cloud back-end, to their website, to their mobile apps… It’s just really the best programming language that can share common business logic, and today Miguel showed you how can take the core business logic written in C# and then embed that into your iOS and Android app. That’s when we started the pivot to the – I think that was the first slide we showed, and we’ve been showing that slide for the last three, four years, which is our “Any developer, any app, any platform.” That was a core strategic pivot we have made, and everything really ties with that strategic pivot in terms of “Well, how do we engage with all the developers out there and what does a meaningful engagement look like?” If we’re only helping people running on Windows and targeting the Microsoft platform, that’s very far from every developer and every developer team. And the strategic pivot we actually decided on is that we want to – and it’s very much tied with the new Microsoft mission when Satya became CEO… We wanna empower every person, every organization to achieve more, and how that comes down to us in the developer division space is that we want to really empower every developer and every development team to achieve more. And of course, that huge pivot we made is that Visual Studio was really, for a long time - and that’s the old meme we’re talking about - people think about it as a product that only runs on Windows, that only supports Microsoft platforms. Yeah, and that is another great question, because you’re exactly right - changing a software process doesn’t necessarily change the deliverable. So it was a major transformation that we had to go through, and that transformation happened with every single major Microsoft product line, to say “Well, how do we really take that huge box software mentality and think about every piece of software we ship in Microsoft as a service, which you make incremental updates quickly, and you really observe and respond to customer feedback quickly?” That’s really the pursuit that we have been on. That’s what the factory, our operationalization was designed for. ![]() I wanna go cross a word out and replace it with a different word.” What we wanted to do was incremental updates to the encyclopedia, versus the whole big encyclopedia, but our machinery only knows how to produce this whole big thing once every three years. I just wanna go inside a chapter in this one book, or I wanna go rip a few pages out. And what we were trying to do was like “Don’t buy the whole set. And I wanna give you a metaphor - imagine in old days people bought encyclopedias they were beautifully bounded, A to Z, you buy the whole thing, you stuff your whole bookshelf. Yeah, so our first quarterly update was VS 2012 update 1, and it was a very traumatic thing for the team, because the entire engineering process was not set up to go do this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |