 But that would be my problem, is like not having the idea, not reflecting on it, because we'll just have to... I know when I tend to want to fix it on something, if I don't know what I'm going to think about it next. Because I'm not afraid of what I think you're really grasping more when I really go. The next step I'm going to show you is open source. You're free to use it. So one of the first issues would be one of the first things I noticed is that they started every Friday from the start. That's nothing great. So I gathered the team together and I just started asking them, we have this every single time you work, every time you work first. So what's the dive into that? What you're going to see now is not what we wrote, what was some stuff that we learned from that project. And then everything was like, I've noticed that we added this feature to a lot of the projects. Or I had to set up this thing this time, and I would like every time we work, we would really help to speed us up. I think this covers any data that should be approved, I set an idea, whatever it is, we write it down, we review it again, and then we apply it to our starters so that we... So the first thing that we wanted to kind of dive into with this was organization. Purpose has a convention for organization, right? It's a little short scope. So with plugins, you have no idea where anything is. With themes, you have a general idea of where the templates are, but that can get kind of gnarly. And I know where a function set PHP is. Oh, I remember that. And mid-time set PHP is blown out many other times. The tutorial of mine says, put this in your function set PHP. And we're like, okay, copy and paste. And so the first thing we wanted to do... Okay, so really the first thing was documentation. Throw a review in there so that anybody we bring out more knows exactly how to use it. Instructions, what is this? What are they looking at? How do they get started? How do they use it? All this kind of stuff. It's amazing when a single file or some instructions can do for your team. So you don't have to expensive every single time. So organizationally, I'm a very good beginner, but we just wanted to trim it up. The templates are not just usually in here anymore. Like, we get work on a big site, you know, templates on top. So we broke it down and said, like, oh, so we have our views. And in there we have a nice organizational structure where people can always find what they're looking. Next up, basically it would be, you know, assets, work, you know, your status, your interviews, your JavaScript, all that kind of stuff. And then, sort of, I wanted everything to kind of feel more object oriented and lower nicely. I wanted to, we use PSR force that things would be namespace, so that if somebody's working, you know, with this example of post-type, in an example where it is, how do I know where this is? Well, because the namespace is post-type, therefore it's in source post-type. So, okay. So that was organization. Like, I just showed you one here. I wanted to be able to, you know, we use a lot of post-tops and stocks. You don't know where it is, so you don't just grab a theme and then do a search all for register post-type and then go through the search list and contact the register date. And then also you have a code that pertains to a particular code. So I wanted, like, a single nice place for it to be. And then it's broken down and you have your slug, you have your labels, you know what I'm saying. And then you have your two little arguments that you're used to register post-type. Well, there's everything that you want. Do you have assets and task runners? So CSS and JavaScript are pre-compilers and using Must-Up. It's not as much. It's also going to have a point where the thing that really turned me off initially was like, the thing that I did not like about time was you had one guy in the team who understood how to register post-type. They didn't know what to do with it. They were trying to write CSS and you had this file written in... No. What's that? So it was just, it was scary. It was weird and Webpack came out and it made me helpful. I still felt like there was a lot of weird complexity. So Larival Next. First up and all, write that down. Larival Next is highly recommend that. That was one of those, you know, needed a solution there. Old tools. We have a mix of tools. We buy all of our guys. How did we do that? It was a constant thing we were observing and reflecting on. And so it made me very happy that. So the last thing was, it's very much a, if you don't know Ph.D. but you still want to build stuff, a loop. But if you're trying to do anything more involved, I just want to know where you're working. We're so quick on this one. We're doing something called open source. Basically it gives you a, your terms, excerpt, list, post, there you go. So we use that on every project. So let me show you an example of what is your title. There's your content. So we use that on our project. It's extensible. You can add all sorts of stuff. If, if I'm going to program, we use a thing, we request a new thing. I already went checking it out. If you don't use it, you might find something in there. Everything I just showed you is as interesting as it is. That is the result of just a lot. I want to give you, help you to just feel empowered. The coolest thing is built. It's awesome. And then a long and half hour later they're like, ah, it's not cool anymore. And I won't tell you. Innovation most often comes from really seeing what innovation most often comes. Identify the cars. Resources, the slides, the talk. If you want to like, see that circle again. Feel free to just throw it in and talk to me. I like to get it fairly on. And then lastly, I know this is pretty weird, but I really like to learn. So I actually threw together a survey. You're just, feel it. You're just like, hated us so much. I wanted to know. Or you're like, ah, that was really awesome. And then, you know, whatever it is, I should be able to throw closing remarks in about 10 minutes. So.