Live data from Hacker News

My current strategy is to not read any of the code written by my agents

twitter.com

21–30 of 65 posts

Re: My current strategy is to not read any of the code written by my agents

#21
My current code base has more tests than runtime code. This sounds far more thorough than that. If you limit the possible productivity improvement to a small portion of total effort, it's inherently also going to be a small improvement.

Which, is fine, but not what most people are hoping for with these tools.

Re: My current strategy is to not read any of the code written by my agents

#23
I 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.

Re: My current strategy is to not read any of the code written by my agents

#27
post #18

This 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).

[deleted]

Re: My current strategy is to not read any of the code written by my agents

#28
post #23

I 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.

What do you mean by "completely backwards"?
Post reply on HN