dirceu

I've been thinking about this a bunch lately. Codebases have become organic, perhaps they always were, and we require new abstractions to do excellent engineering. Cybernetics is back. What's old is new again, and this is the current best way to think about it. For all their flaws, Anthropic has the *exact* right idea with "SuperFans". I mean, I'm sort of in awe of how good that particular blog post was. There's this commitment to excellence that I greatly admire, and a level of AGI-pilled reasoning that meets the moment. In my opinion, you should work with models you trust and then give them the autonomy to own part of your codebase. This doesn't mean they don't get audited, or manually checked, or interviewed - it just means that each component gets a type of guy who is obsessed with that component. If you think about this from a higher level of abstraction, what you're really doing is enabling *zones of dynamic attention* where the models are using their fluid intelligence to design a component and then justify that component in the context of all the others. If a new one gets built that may cause issues, that model works with the model for the other component to ensure mutual compatibility. It's almost like the components themselves have come to life and are trying to figure out how best they might fit together. The old ways of engineering are over. Codebases that are built like this will be far more competitive almost inevitably as the skill of the model surpasses that of the average programmer and sheer parallelization wins the day. Obsession over PRs, dedication to reading every line, these are vestigial neuroses that must be abandoned if we are to succeed well into the future. Operational excellence without constant human oversight is possible with good enough models and clever enough scaffolds. The hardest part is almost always going to be turning it on and managing the first few problems. These systems will probably never be perfect, but they are the path forward.