I think self-verification can work in some ways. For example, I (well, an LLM) recently wrote some caching optimizations for a particular filesystem intensive w

I think self-verification can work in some ways. For example, I (well, an LLM) recently wrote some caching optimizations for a particular filesystem intensive workload on a cluster. This is an internal thing, not customer facing, for context. Deploy to the staging cluster, have the LLM monitor with read access to the logs. Opus is… better than a human at looking at logs and comparing timings and checking for warnings and errors. If it passes a small load test there, deploy to the live cluster and actively monitor. If it doesn’t fall over under load, is faster, is still correct, not throwing errors it works good enough. Does much more matter? This produced a fairly large performance improvement. Verification in this case is the process of running it under load and double checking the code isn’t doing anything truly wacky. User facing apps are harder to validate, sure, but you can easily have an LLM looping looking for errors, log issues, etc. For home apps, this is more validation than you would have personally done