 So my name is Seb Sebastianova from Montreal Canada. I am an office Dave MVP for now more than four years and a half Whatever that a half I've been doing SharePoint for a long long time. I'm a product evangelist and partner manager for a company called Follow Internet where we manage a bunch of different partners here in the US and in Canada and Been doing that for now more than 12 years So my background is So actually I was born in SharePoint and I like to say that I've been in the internship went out of college and Someone asked me do you know anything about that net? I said yes, I'm very proficient in that net So you know something about SharePoint? You get you want to get a job so you say yeah And then you just started that and then the next day you know that you're working in SharePoint design and info pad design in 2006 And then my background is really dev focus. So I've been from there I I moved to the real dev side of things working on in on SharePoint 2003 2007 2010 2013 2016 and now in the cloud Five years ago, I did a big switch from back and dev.net and everything to entirely JavaScript and CSS and HTML I bought a Mac at the time was like cannot do any visual studio stuff in here So I just switched entirely to the to the modern stack and since then that's what I'm doing spend a lot of times I've been working with the SharePoint framework since is Early early early days where nothing was actually working but since I've been working a lot to Understand the different concepts in the framework. So and that framework also brought me into the react world and all the web pack and everything So that was a good way to start that modern Web dev stack. I've been working on like what what maybe two years now that the SharePoint framework is out And still today. I'm having a bunch of fun with the with the framework. It's awesome The SharePoint to a framework today is for me a very very good Step like I think it was something that was needed in the SharePoint world Especially in the dev world where it was a nightmare for us to customize any SharePoint experiences through any of the Other customization options we had including add-ins and all that stuff I I still think that it's not complete that we need more than that to be able to actually really really really offer a nice experience to anyone Building amazing solutions for now. It's pretty much only web parts and extensions and that is for me not enough Especially coming from a very very deep net background in there. It's we need I know working the team is working hard on making things happening, but if we need to switch There's not enough in there for me to actually switch and build all my my solutions Entirely on the SharePoint framework. So for now, that's how I feel about the frame It's good first. It's good. It's public It's also good that we see what gets removed from from the roadmap quite interesting to see I think The roadmap for now is very very very like it's not long-term. It's at mid-term. It's very very short term We don't see a lot of what is going to happen in the year or so There's a bunch of different items and there are cool that we know that are requested by all the devs and that are That needs to happen, but I want to see more than that. I want to see like The complete story. I want to see where what's what you're aiming for today And that will help us in shaping our own solutions to Try to take advantage of at least the mindset that we'll need in a couple of months or in a couple of years To be able to build something today. That's going to be still relevant in a couple of whatever version of the SharePoint framework I would say that's the the web parts Just because it's the only part that actually really work today Though I really think that there's a lot of cool stuff happening on the extensions side If we go like somewhere else and just what the feature of the framework is I think the the stack is what is absolutely amazing and I've been talking to a lot of devs that are not SharePoint devs because when you're SharePoint devs, you're like cursed Those devs are like, okay So I guess you're still doing like dot net stuff in the web page form and blah blah blah stuff that are pretty boring now Like no, actually I'm using webpack and I'm using all those different technologies like oh, that's interesting Actually, I will try it and I'll let you know and some of my friends actually try it. It's like, okay That's that's decent. That's interesting. So that's probably what is the most Appealing for me and appealing for the community as it's not only about SharePoint It's about the stack and then you just use whatever you want in there. So that's I think that's something that is pretty cool And that's gonna be a key For the SharePoint framework to survive through years as there's going to be a huge community around that Well, that is an easy one Been an Angular dev for the last four years So I'd like to be able to as you know, that's screened. No no framework React and knock out whatever I want to have Angular there and be able to have natively Angular included in that Framework the reason why is that I think there's a lot of People around the Angular community that would help I don't think Angular would like resolve all the problems I think it's just one use case that is added on top of the framework But if I can get that I will be extremely happy extremely extremely happy first I want to change the way the way the That open source community should work. So for now, I'd like to be able to change stuff in the in the SharePoint framework I'd like to help the Microsoft team to understand how we actually dev and everything and go in and Do a pull request on the yo man generator or help them in understanding how I want to do stuff I know the github. There's all those issues we can put that but that is questions answers and then Thanks for your feedback and that's or it's going to be there in two weeks or in three weeks I'd like to be able to fix and help Microsoft building that I think the dot net team did an amazing job when they opened the code and actually they add plenty of Pull requests and lots of new code from the community to be injected in the dot net Stack why not the same thing for the SharePoint framework? So that would be out what I would change is to open up to the community There's a bunch of excellent devs that will help them to build what is required I'm thinking I can in in in the past when when SharePoint was still a thing of the back end It was like that tool Siki as Siki as dev that was actually built by community for real like for real business scenarios Where dev needed that kind of stuff if I can have the exact same thing with the SharePoint firmware That would be awesome. Let's let's take the entire SharePoint dev community Lots of them are still doing on-prem stuff with dot net and all of that. I think one of the biggest challenge is The transition from that old model from dot net from timer jobs from event receivers To something that is more modern and more cloud-enabled and more SharePoint framework type of thing So that means changing your entire build process changing your your language you're using changing to javascript Go into the async mode and not to to to be asking that is that is in sync. So that is something that is extremely Challenging for a dev. I think it's doable. I think there's a lot of like parallels that can be done between typescript and c-sharp or a ms build and Webpack or gulp or whatever But that is a challenge that people if if you're like really really really into the dot net dev It's a hard step. So it's it's kind of hard to okay I will leave my visual studio on the side and I will now use Console and visual studio code and change my entire tool set So that is something that for me is very very challenging especially for for a big large enterprise that build a skill set on top of their team and now they need to Put that aside and start over. So that's one of the biggest challenge So I'd say that a where I want the framework to be in maybe 18 months is I want to have the complete story Or at least feature parody with what we have on premises today um, but not only feature parody but also come with brand new ways of doing things brand new Features brand new capabilities that are not currently available in the SharePoint world Very very rapidly. So short term um, I want to be able to easily deploy easily customize anything I'm doing on the SharePoint framework that means The announced a tenant wide deployment for SharePoint framework, but I want more than that I wanted to be able to deploy my extensions. I want to be able to have those Modern hooks all over the place with web hooks when that exists and everything and I'd like to see a lot more tools and modern Like features modern paradigms in the in the SharePoint framework to happen But still I really we the like if I look a lot Longer than that 18 24 36 months. I just want to be the de facto SharePoint customization story I want them to completely ditch the old model and And assume that this is a new model and that this new model will rule the rest So they will bring it back to on-prem as much as they can and then just use that and work hard on making things happening So I think that my one advice for all enterprise devs will be to Start investing time in learning about those new technologies forget the SharePoint framework I don't care about the SharePoint framework for now Learn about the stack learn about webpack learn about typescript learn about javascript even if it's something that is out there for a long time Uh, still people are not Experts in that field. So I started by learning the foundations then afterwards Learn like the basic SharePoint framework process from the yo generator to the gulp serve and to be able to package that I think to know the foundations will help you Build amazing solutions. You don't care about how you write your web part or all you write your extensions But if you know what are the customization available Uh, how you can customize a SharePoint solution and how you can build a web part using the foundation Technology typescript and all of that then I think you'll be in good position to be able to move forward Um, and also start looking at cloud paradigms. So stop thinking about what's a web like I want to be able to time or job No, think somewhere else go see azure opportunities go see azure functions You use what the cloud has to offer to actually implement great SharePoint framework solutions