Sounds a bit like what Claude Plan Mode or Amazon's Kiro were built for. I agree it's a useful flow, but you can also overdo it.
Seems like a lot of work to still have data that can be exfiltrated by the US.
One bug is all it takes to compromise the entire system.
The monolithic UNIX kernel was a good design in the 60s; Today, we should know better[0][1].
It's not uncommon for the bugs they found to be rediscovered 6-7 years later.
Profiting from selling their patchset is not the whole story, though. grsec was public and free for a long time and there were many effects at play preventing the kernel from adopting it.
This resonates somewhat, but for a different reason. My mental model is that there are two kinds of developers, the craftsmen and the artists.
The artist considers the act of writing code their actual fulfillment. They thrive on beautifully written code. They are often attached to their code to a point where they will be hurt if someone criticizes (or even deletes) it.
The craftsman understands that code exists to serve a purpose and that is to make someone's life easier. This can be a totally non-technical customer/user that now can get their work done better. It could be another developer that benefits from using a library we wrote.
The artist hates LLMs as it takes away their work and replaces their works of beauty with generic, templatized code.
The craftsman acknowledges that LLMs are another tool in the toolbelt and using them will make them create more benefits for their customers.