 Now, I mentioned before that speed is something, at least in my mind, that's a game of interest. It's incriminal things that stack on each other. You can stack one thing, two things, three things, a hundred things, two hundred things, and all of these stats will enable you and your team to move faster. So here are some of the things that I've thought, and I've found works work really well for me. Again, you want to AB test to make sure that it works in the context of the work you do, too, right? Well, you saw before in the schedule, that was batch processing meetings. What I do at all times is I think about how do I optimize for deep work? I believe in code-developing for products, right? It reduces your cycle times, it increases the likelihood that you actually have a product that works, and you have people who are vested into your product from the start. Time-shifting schedules. As crazy as we can have 5AM, it is for some folks that works for me. One of the things I found to be, again, they don't have to be big things like a complete re-haul of your schedule. It can be as small as using both a Windows and a Mac machine at the same time. For those of you that code, I don't know how people code on a Windows machine, but I've never been able to do it. So I code on my Mac and I use my Windows machine for everything else.