A small add on to this: I constantly emphasize to everyone I work with how important it is to THINK about this stuff. It sounds cliché and obvious, but it goes much deeper than that. Spending real, dedicated time simply thinking about ideas, structure, and optimization can compound in ways that are not immediately obvious. For years, @WillAmbrus and I would spend hours just thinking through problems. Long discussions, voice notes sent late at night or over the weekend, and constant back and forth around a single idea or potential optimization. What if we test it at a different time of day? What if we isolate this sector? What if it is conditional on a specific volatility regime? What if a certain agent behaves differently and the signal becomes stronger? That process has not changed. Even now, over weekends or late at night, our Slack channels are constantly active with the team debating ideas, stress testing assumptions, and pushing concepts further. I have often encouraged people who work or have worked with us to step away from the desk and spend time just thinking about an idea. Sometimes that means deliberately not coding or staring at data for a few days. Taking a few days off to go and hike, or do other activities while thinking about the problem can help. Some of my biggest breakthroughs have happened while driving alone, in the shower, or doing something completely unrelated. It can feel intuitive to just keep grinding, writing more code, running more tests, and immersing yourself deeper in the data. But I firmly believe there is a point where stepping back matters more. You let the idea breathe. You let your mind do the work. To me, it is no different than training. If you max out every single day without rest or recovery, progress eventually stalls. Strength and growth become suboptimal. Thinking works the same way. Without space, you cap your upside.