Which, is fine, but not what most people are hoping for with these tools.
My current strategy is to not read any of the code written by my agents
21–30 of 65 posts
Re: My current strategy is to not read any of the code written by my agents
#22Re: My current strategy is to not read any of the code written by my agents
#23The really interesting thing to me is that formal verification wouldn't have helped there either -- it would have just written a mathematical proof of the correctness of the backwards feature.
Re: My current strategy is to not read any of the code written by my agents
#24> I’m significantly older than you. I started coding in the late 60s. Any opinion that starts with such a blatant appeal to authority can safely be ignored.
Re: My current strategy is to not read any of the code written by my agents
#25When my nephew went into computer science, I had to warn him about the bracelet cult people
Re: My current strategy is to not read any of the code written by my agents
#26Re: My current strategy is to not read any of the code written by my agents
#27This is the dude who ushered in the age of nonsensical boilerplate-ridden OOP code where you need to go down a bajillion of abstraction layers to see the actually implementation. Makes sense that he doesn't care about the bajillion lines of code AI produces as long as it looks good (on the surface).
Re: My current strategy is to not read any of the code written by my agents
#28I keep posting this but it keeps being relevant. I had an agent implement a feature completely backwards. It wrote a whole bunch of tests proving the correctness of the implementation. All the tests passed. The really interesting thing to me is that formal verification wouldn't have helped there either -- it would have just written a mathematical proof of the correctness of the backwards feature.