 Good afternoon, good morning to everyone or good evening if it's in your time zone already so late, so I'm very happy to present you what you have done in the last weeks and what our goal and our target is for the next weeks. So, I already posted the slides in the GU channel, so please send questions there or also in the Zoom chat. I'm very happy to welcome another two new team members this month, so Dennis Tan and Lukas Eibert started, both are based in Germany. And we are very happy to have you on board and we are really looking, everyone is looking forward to work with you and see your contributions. They are already deep in code, highly motivated, so it looks like we had, we made really good choices there. They are currently getting on board with our specific frontend body program, so if someone is interested also from other groups, we have started something directly targeted frontend engineering, so this worked quite well with our last candidates and we got really good feedback on that. What are our accomplishments over the last five weeks about the frontend RCRs of Q1, 2018 we have reached with the developers on 10.5, 80%, on 10.6 we haven't reached a really good number due to several reasons we have reached 65%. The target that we had of 300 bucks, 300 close bucks in the time period we already reached that last Friday, so I hope that we get even more close than that one. The dispatcher JS and the jQuery upgrade are done, those are big refactorings that were done by Jacob's team, they are also merged. There is a side speed IEO Docker setup done by Jose, thanks for that. I hope he can hand it over this week to production so that we have a full Docker Kubernetes setup that automatically goes against github.com and this reporting all the numbers into graphite and then we have ongoing performance reports there. Overall, our technical directions, we are making quite good progress, we are moving more and more to view and also bigger view applications, so having better data storage, having routers in there, so we are going more in the single page application direction. And it's working quite well, especially with reusing components, so we have components that are reused by different product parts and we have now made a lot of experience of writing something so it can be reused easily, making it more generic and basically have a very good impact on our development time because you simply take the components and send something there and suddenly you have comments rendering, by example. The technical team also finished their big refactorings as said, you can read up there more. We are in the middle of introducing automated code formatting, so we are using a tool which is called pretty IEO to do automatic code formatting on save in our editors, so we are adding this soon. And one of the next steps will be also that we are doing this on pre-commit, so no front-end code is anymore submitted to the CI or CD that can then fail there on the dinting, it's everything's automatically formatted and linted beforehand before you even can commit. But our biggest challenges, let me take a look. So, yes, still the quick scaling is definitely one of our highest priority to integrate all two new team members. We froze the hiring so that we are not overboarding the team with too many new people at the same time, but as said Q1 is ending soon, so the hiring will be opened again soon. And the other big task and the other big priority is really hitting the 100% delivery. I think there are a lot of different topics that are being tackled, is it being the feature freeze so that everything is already on the mark when we start our release cycle, but also that we on our hand have to more pre-planning, do more intensive planning on the different tasks and how we work together with different teams. I think that iterating pretty well that this is getting improved and is being more productive. What are our plans for the next week's implementation goals? Reusing, as I said, is a big topic, so we have better reusability that is going hand in hand with the CSS refactoring that the technical team is working on, so building components that are taken from the UX from designkitlet.com and bringing them to life. The merge request view, so everything that you see on the merge request that is currently one of the slowest parts of the application because simply too much is happening there is currently converted and refactored already one big part was already merged. And far this doing a great job to bring in over all the different parts, so you have a complete view, single page application, you can switch between the diffs, it's much faster, you have skeleton loading, so we are looking forward to reducing the time that this page takes at the moment. And as soon as we have the view, we have so much more possibilities to even do way more improvement, performance improvements, especially with scrolling topics like this for the merge request, which are always a pain. So, and the other big topic is as we are growing as a huge team workflow. So, we're trying to do it like automated on the automatic side with tools like prettier, also we're looking at boilerplates, but on the other hand also on documentation so that the extent and reshape our documentation that we get automated documentation from our components and utilities. And on the other hand also boilerplates so that we have boilerplates, for example, if you want to write a new view reusable component as a boilerplate with a checklist in there what you need to do there, what are our criteria they are on the styling, etc. Yeah, and that's something we are trying to iterate so that we grow as a team and also on how productive we are and reduce time spings that we don't need that we are doing repetitively. Yeah, that's it. Now the main part comes. Who has questions from John Norfolk. Yes, there was. There is also a thing that is going on that side speed is reporting to permiters. And there was already work done. What we are currently simply doing is to bring side speed I or currently already in the process is simply do it has a lot of reports so it can help you with. The permiters stuff that is target you can talk to Josh about it. He knows all the details. There it's really targeted the moment on 123 for data points, but what side speed I hope you give us from our perspective is simply hundreds of data points at the same time they do video recordings in slow motion automatically so you see which parts of the page are loading. They give you detailed things there's a coach implemented so this is really target for us now to improve the performance. And on the other hand, yes, this that side speed is a big topic also with the permiters team to move the forward. Yeah, after 10.5. So there is already everything saved I see so that something we should take a look at it. Do we still pack chairs into one file for all pages by Dimitri. No, there is the big thing that the technical team was working on Boston dispatcher chair stuff. So splitting up and doing code splitting more and more was a big topic there to do dynamic imports. There are still some configurations need to be done to do even more bundling but we are having now way more bundles by example the idea has its own bundle. But with all these refactoring we'll get even more and we can reduce the whole size and also the libraries that we are loading because exactly that thing is one problem that we are loading JavaScript of pages that most of the people will never even see. Yes, that's the ultimate goal and have only in the manger is something in the main package something that is really loaded or only every time something like navigation or something like that. Any other questions. I do the classic countdown. It's a five or four if you're not typing fast enough then please simply speak up. Otherwise, I wish you all a happy day and see you at the team call. Thank you to the whole front end team for their great and awesome work and thank you everyone for listening and also your questions. See you next time.