Process debt: the CI/CD analogy for agent-speed teams

absolute center of truth that prevents invariants from entering your codebase. And what I really wanted to talk about today was not any one specific thing. But it's this general concept. You can build incredibly complex systems without traditional systems like code reviews. You don't You can work in things in parallel, and you can use AI however you want without requiring any sort of standardization. But the most important part is you have to be incredibly thoughtful about how your engineering team actually uses the systems under the hood. When we started building BAML, I didn't think it would be possible to build some of the software we did. And just yesterday one of our engineers built a partial C compiler purely in BAML. So, when I start pushing the boundaries of these systems and you stop reading the code, in some ways in my mind, it releases the floodgates for your engineering team to actually cover the gaps of what existed in your old process. Have you ever worked at a company that had no CI/CD? They said adding CI/CD would slow us down. They They do slow down for 3 months while they add it, but after that, they move a lot faster. Our processes have to evolve if we're going to ship at agent speed. And remember, this is the least amount of slop your codebase will ever have to this day. So, just embrace it and start fighting it back.