zavec
Joined 2 years ago
Joined 2 years ago
Maybe the solution is that I should just be running the entire thing in a sandbox in any case.
One thing I've been worrying about recently is the notion of comprehension debt and making sure the humans can still understand the system (so as to be able to do incident response or something if the LLMs are down). The slower, more methodical workflow described here should definitely help by allowing checks like proper docs whenever a piece of the architecture changes for instance, but I'm curious what else could be done to help the humans understand as much of the implications of what the AI is doing as possible.
Edit: having the code author and reviewer be completely separate like you described below is also probably pretty helpful for making sure changes are comprehensible from the outside.
(Or computer mad scientist? Whatever (mad scientist) && (computer scientist) is)
It's definitely not so good these days, but a format called premodern is getting more popular. You may find it worth looking in to that one.
Socials: - github.com/ian-fox
---