 Hi, so my name is Vincent. I'm based in Montreal, Canada. I work for TutuLid as an Office 365 and Azure developer and I'm also an office servers and services MVP for three years now and yeah I've been working on SharePoint for a couple of years now. So I started working on SharePoint ten years ago I would say first as an IT pro actually and the biggest thing I liked about SharePoint is to understand properly SharePoint you have to do both IT pro and developer. So this is why I also had some developer background way back then in PHP and this is why I liked SharePoint and so I started learning .NET and SharePoint development and I got into there and well basically I'm still there ten years after so yeah this is my background. So I don't know how many hours I spent on the SharePoint framework I would say like they announced that to us some more than a year ago at the MVP summit I was looking into that here and there and then I was playing with it and trying to understand what was technology and how it was working and so I would say a couple of months at least and a few thousands hours at least but the great thing about with a SharePoint framework is it's based on modern web technologies so if you know webpack, gulp and type script and so on and so forth you already know some other stuff right and I already had experience on those things before playing with your SharePoint product. I think it's great effort from Microsoft at large to transition a very old product if you take it in IT terms and IT years right into the modern web development and so on and so forth and also into important source and it has been a tremendous change. I think it's a great promise or like the goal is noble and we still have a long way to get there though. We only have the web parts for now and last week they announced the common extensions and so on and so forth and they're adding little by little but we still have a very long way to go. I like the roadmap because it captures a lot of things we've been asking for many years into the SharePoint space. For example when you think about ALM and DevOps processes which I've been talking about quite a few times now in the past in the SharePoint space I mean I like the fact that they finally understood that we need that stuff we need APIs we need tooling we need proper documentation around it and they're working on providing it. I might be a little bit impatient I would have liked to have seen that before maybe around the add-ins adventure and so on and so forth but yeah I like the roadmap and also access to the graph and I have a bunch of things that make a lot of sense in today's environment and development patterns. I think the greatest change we made so far compared to the other development models is enabling unit tests first so whenever you create a new SharePoint framework project right a new SharePoint framework part day one you get unit test support which we never had in SharePoint and which was super costly and so we never did it to be honest right and I think it's going to be a great addition to our tooling and methodologies and so on so forth to make sure we ship quality other quantity or whatsoever we were used to do. It's a tough question I would add many things the first one would be probably stuff around the provisioning with the full trust solutions add-ins and so on and so forth. Historically we always have been able to provision stuff lists and whatever you name it right and we don't have that in SharePoint framework which is kind of a bit confusing. Of course there is the PNP provisioning initiative but so far I haven't seen any announcement or any information about it and I would like to have that also like to have stuff around the graph around ALM and so on and so forth but maybe I'm impatient. The one thing I would change is probably the way they interact with the community I get the fact that you have two things coming into play into the SharePoint framework right you have the SharePoint server bits that are part of the product and it's Microsoft code and they have to keep it on their end right but then you have the SharePoint framework bits that are supposed to be open source and they are based on open source tools so I would like to have seen way earlier the source code of a framework open source so we could help them moving forward and getting faster and I think right now they they are not like benefiting that and it's lacking in the framework itself. So from a SharePoint developer's perspective I think the biggest challenge around the SharePoint framework is to transition from server-side technologies, non-open source stack and backend development to something which is more open source something which is totally different from what we were used to so the learning curve for SharePoint developers is big but that comes also with another perk is I will be able to talk with my other open source developers friends and they will be able to be involved in what I'm doing so so I think it's kind of a trade-off right but it's hard for former SharePoint developers to transition to that so far. So my personal thoughts around that is I think and they have started that transition a couple of years ago they started saying that SharePoint was more and more a service and less and less of a platform right a couple of years ago and they kind of kept that message going on over the years right and also when you take into account Microsoft Teams as a platform to me it would make sense somehow that the work we're doing on the framework and on SharePoint and the work which is done in Teams should connect at some point and be almost the same thing right if you take a side branding and so on so forth what you want to support is you want to enable users to do stuff and everything is going to be in Teams so not only SharePoint but planner notes and so on and if you want to enable users the more services you can leverage out of the box and the more content you can provide out of the box better it's gonna be so my guess will be SharePoint is going to be the API and Teams is going to be the integration platform so that's my personal guess if I had an advice it would be probably for Microsoft to provide guidance around full trust solutions add-ins frameworks and also the future around that because a lot of people are asking a lot of questions around it and they don't know what they can leverage at what point on time now but what they will be able to leverage in the future and how they should transition for different scenarios this scenario in that scenario also having some kind of support for the backend services into the framework would be good maybe include a Docker template or norm template for Azure whatever it is right so we could provision stuff to do batch jobs to do queuing and heavy lift and shift on the backend would be awesome to have that in the framework as well