 So, we are doing a combined front-end group update with about the AC team and the DC team, me and Jacob together today. Let's just jump right into it. What are the progress that we have done over the last five weeks? Mainly one of the biggest achievements, which was a great teamwork over a lot of teams and with a lot of involvement of different people was the move to headless crew in all our testing so that we have now faster tests, we have more accurate tests compared to the actual rendering because phantom was always a little bit off and there were a lot of workarounds, especially for phantom.js that were removed. My grading is also working at the moment on a blog post which I'm really looking forward to it, documenting all the steps that we have done, all the big rocks that we have faced over this process and documenting this also to the outside world which is, I think, very interesting on such a large scale. Another thing that we have always kept an eye over on improving our performance, our front-end performance rendering time. So we have done constant improvements. In the past releases we have done bigger things like lazy image loading, et cetera. Right now we are already focusing more on a lot of smaller stuff, so we have changed the way how language files are loaded that they are loaded, only the files that you actually have that English is not loaded additionally, et cetera. We are looking very deeply into under-optimization so that only the JavaScript that is actually needed on the page is loaded. And one big topic that we started were inline SVGs so that all the inline SVGs that we had so far in range are now converted to SVG sprites which is exactly the next slide. So we have an SVG project which is an external repo for all icons and illustrations. The really nice thing is that we were able to change the workflow over that so that the SVGs are managed now mainly by UX. They can add the icons there. They can preview the icons there. Also the front-end is adding stuff but mainly the UX is doing all the work on the icons. In there we are reusing KitLab CI and CD for automatic optimization and spriting. So all the SVGs that are there in the folder are automatically optimized. They're combined to one file so that they are in this sprite which is then loaded much faster and is cached and which is a great achievement, I think that we have this automated and we want to even automate it more. And we have, on top of that, we have also a preview application as one of the main things that you do during a daily routine is searching for icons. So on KitLab Pages we are hosting this small view and next application where you can search for icons, simply click on it and you can copy it so that you can insert it directly in your code and reuse it. So all our illustrations that we are using and are in the RIP at the moment are previewable. Yeah, another big thing that we stepped into was GEO. So the AC team is now taking care of the GEO front-end. So if you have anything regarding that, simply ping me and you can find resources or can plan stuff ahead. Another big thing at the moment is for us hiring and I will hand over to KitLab. Yeah, so between the two of our teams, we're hiring five front-end engineers. We're revamping the hiring process. Docs are forthcoming. We've already implemented, in part, some of this revamped and it's already showing really good results in the candidates that we're getting. So we'll share those docs shortly. Team concerns, Tim. Yeah, still that's something that we still have in July. So especially with the performance, we still see a lot of stuff that we can improve and that we want to improve. But now we are getting more to the point that especially stuff that we need also from infrastructure and the back-end that needs optimization like G-CIP in finalization, the CDN finalization, where we are very close to activating the CDN. And the other big topic is resizing images. So resizing images to the exercise that we are displaying so that we push forward on those topics because they would be the next big, big, big steps to improve our front-end rendering performance overall and also reduce most probably the load that gets on our servers. So what are we currently focusing on? Those are our quarter four OKRs. And we have one of the biggest OKRs is simply crush 280 bucks and 120 new unit tests for both teams. Yeah, Jacob, give us a little bit of an overview. Yeah, so we're just splitting up between the two teams. We did some for me approximation estimation and we figured this is how much we can do. So it comes out to about two bugs per developer per week for the whole quarter. And we've actually been able to step ahead of this and we're getting ahead of this estimation. So we're actually doing really well in this. So this should really just absolutely tackle a ton of the major bugs that we're having. And then we're also getting ready for Webpack by we're doing these modules. You can see in the issue what we're doing there. We're taking the global code and we're making it modular. We have a huge list of things that we need to do in there. And we're just going to go in through them one by one and taking the situations where the code is global. And we're just turning them into modules and we just submit a merger quest for each one of them. But every single one of these things will just make such a huge thing, huge improvement on our performance. So, Tim. Yeah, one that's especially the modularization will be a big step forward for creating the next bundles, which is another topic that I'm focusing on. The AC team, which is the library updates and that pack bundle optimization, which does what does this mean? We are moving all our non-managed libraries that are still in the code base to yarn. We remove unnecessary libraries. So we take a look. Is this by now doable with just vanilla chower, script, et cetera? We are in the process of updating all these libraries to their latest version. And we're doing one merger quest per library so that they are done in parallel. Some of them work like you upgrade them, works. Some, a lot of others also have major changes because they are simply a little bit older. But what we want to gain out of this is on one hand performance improvements. We want to reduce also the dependency trees so that some libraries are dependent on a version of two and the other one is dependent on a version of four. So if we upgrade all of these libraries, most probably we'll get to the same dependencies of these background libraries. We get a lot of free packages from them. So I've seen already simply with the first three library updates, I was able to close also two free bugs simply by doing the upgrade because they were fixed in the library. And we should be also able to get smaller bundles over this task because a lot of libraries are now updated to the point that they use vanilla stuff that they don't need so many dependencies. So they're also getting sometimes smaller. And another big thing is then after these two big major steps to create really focused bundles on the specific pages that we need that we do more intelligent pre-loading that we do perhaps also loading only of bundles that are specific to specific browsers so that we only by example do transformation of the code to IE 11 but only then if you have IE 11 have a separate package and stuff like that we have much more possibilities in the future. As I said before, a big task is the SVG icons. But of course this means replacing a lot of icons and we have really, really, really many references to icons. So our current target at the moment is mainly to go from all the inline trace icons. So what was done before is that each SVG icon was simply inline into the HTML. What does this mean? So if you had the same icon, this was inline like 20, 30 times but was simply loading the HTML size. And simply by having now just a reference we are able to reduce the HTML size again. And we are also in that process getting rid of duplicate icons. We are updating the icons to all the wonderful icons that were created by Hazel so that we have really our own GitLab icon set. And in the next step and also in parallel at the moment, we are replacing font awesome icons which are like general system icons to become these GitLab special icons. Jacob. And sorry, yeah, thanks. For the DC side, we had refactored the issue comments in Vue.js and the cool thing about it was that it was kind of like a seamless process. Most people didn't know except that the issue comments just sped up a lot. And we have not been getting the same comments that the issue comments are slow and everything. So still the merger quest discussion comments are slow and that's the next big thing is to refactor all those. And that is a process that's currently underway to make huge improvements to the performance of the merger quest discussions because currently for larger discussions it's a huge pain in the butt. But once you refactor it to Vue.js then you can begin doing a lot of the other huge performance improvements from there because it's a good base, it's a good foundation to work from. So that's just, it's gonna be such a big deal. It's a little tougher than doing the issue comments because it has a lot more to it. But it's just going to make such a huge difference for the future of GitLab and the speed. So then finally there's any questions, feel free to ask them out loud or post them in the chat and give you a little bit. So thank you everyone. If there are no more questions until the count of three I am glad to end this from a functional group update. So it's a three, it's a two, it's a one. There is a dog, you get the additional bonus dog. See you in the team card. Thanks everyone.