| ▲ | woeirua 4 hours ago | ||||||||||||||||
You got downvoted for speaking the truth. HN has a strong anti-AI contingent. They won’t concede until you can just ask Codex or Opus “find and fix all the bugs in this codebase”. We’re not there yet, but soon we will be. Then what? | |||||||||||||||||
| ▲ | maxbond 4 hours ago | parent | next [-] | ||||||||||||||||
More likely people thought GP was missing the point; "MTTR-optimized YOLO deployment" only succeeds against recoverable errors and acceptable periods of downtime against errors that are detected quickly. You could have a bug silently corrupting data for months, and that data may only be used by 1 critical process that runs once every quarter. So you could introduce a timebomb that can't be gracefully recovered from (depending on the nature of the data corruption). So the point is not that agents cannot find bugs (they certainly can), it's whether you can shirk reviewing for bugs if MTTR is fast enough. There are circumstances where YOLO is appropriate, but they aren't the production environment of a mature application. | |||||||||||||||||
| |||||||||||||||||
| ▲ | 4 hours ago | parent | prev | next [-] | ||||||||||||||||
| [deleted] | |||||||||||||||||
| ▲ | hansmayer 4 hours ago | parent | prev [-] | ||||||||||||||||
> won’t concede until you can just ask Codex or Opus “find and fix all the bugs in this But this is just holding the Slop Companies to the standard they declared themselves! Just recently, the CEO of OpenAI babbled some nonsense on twitter about how he hands over tasks to Codex who according to him, finishes them flawlessly while he is playing with his kid outside. > but soon we will be. Ah yes, in the 3-6 months, right? This time next year Rodney, we'll be millionaires! | |||||||||||||||||