“Senior engineers have been through an apprenticeship. They were a blacksmith at some point. They learned how to make a sword, and then suddenly there are machines making swords. If you work at the factory, do you really know how to make a sword, or are you just watching the machine stamp out swords? A senior engineer can deploy agents and produce effective code with low defect rates. A junior engineer can use the same techniques and generate higher-defect code.”

…of deploying these tools at scale. And I think it's actually counterintuitive, but it's a complicated situation. The senior engineers have judgment. They've shipped things, they've written artisanal code, they've handwritten code, they've deployed it into production, they've been burned. They

broke prod several times, right?

You know, with a lot of folks I talk to are building software factories, right? To go with the factory analogy, they're building plow shares and not swords. But the judgment has to be engineered into the system pretty sort of explicitly, right? And I think codifying that sort of ties and knowledge…

We've been experimenting with a few things that are interesting, but I don't think are like cures. You know, we have this like concept of context graph that encodes institutional knowledge. It's just like a shared memory bank, like a company brain, if you will, which we're hoping to like be able to…

Another issue I've seen, you know, in a lot of larger engineering organizations, you lock down the tools, the languages, the things that any developer can use, right? With AI, it seems like I've talked to folks who their organization just has thousands of skills, many that do the same thing, little…