Abundant code generation creates a critical unsolved problem: nobody knows how to manage code quality and human attention to engineering when enormous amounts of code are being generated and nobody is reading it.

Well, the anxiety that I see is like if you can generate an enormous amount of code and no one is reading it, you don't know the quality of the code. Nobody deeply understands the code base and there's more fragility, right? It's like the slop problem, but instead of it being like vibe coding slop for random websites for non-technical people, it's vibe coding slop in my actual production code base for every lazy engineer, which is every engineer. I think people are like looking at some problems of actually do you think ticketing, ticketing systems are like at risk, but I think the broader problem that Jira could go solve or new company could go solve is like nobody knows how to manage that issue of human attention to engineering. And there's a bunch of ideas like testing and smart review, just let agents do it, formal verification. I think it's like open season around this really, really big problem.

verbatim transcript · starts at 10:09