Lenny Rachitsky describes the "dark factory" pattern for AI development: code generated, tested, and deployed without human review, yet still meeting professional standards. Early experiments show which practices work when building trustworthy software entirely through automation.
Chapters
The really interesting future is something people have been calling the dark factory pattern. Right now, if you're a professional using these tools, the way you do it is you tell them what to build, and then you look at the code and you review that code really carefully and make sure it's doing the right thing. What does it look like if you're not reviewing the code, but you're also not vibe coding? You're not throwing everything to the wind and seeing what happened. You're applying professional practices and quality expectations to code that you're not directly reviewing. The reason it's called the dark factory is there's this idea in factory automation that if your factory is so automated that you don't need any people there, you can turn the lights off. Like, the machines can operate in complete darkness. We're trying to figure out what that looks like and how we can responsibly build software in that way right now, and making some quite interesting discoveries about things that work and things that don't work. But that, to me, is the next sort of barrier.