News for hackers. Stuff that matters.

A comment on CriticGPT: Finding GPT-4's mistakes with GPT-4. Parent comment

Re:CriticGPT: Finding GPT-4's mistakes with GPT-4 by okdood64 on Thursday June 27, 2024 @02:41PM (#40813619)
> How is that different from junior devs writing bad code previously?

Because if it's bad, at least it's simple. Meaning simple to review, quickly correct and move on.

[ Parent | on HN ]
Re:CriticGPT: Finding GPT-4's mistakes with GPT-4 by crazygringo on Thursday June 27, 2024 @03:19PM (#40814027)
Like I said, with "object-oriented mostrosities", it's not like it was always simple before either.

And if you know a solution should be 50 lines and they've given you 500, it's not like you have to read it all -- you can quickly figure out what approach they're using and discuss the approach they should be using instead.

[ Parent | on HN ]
Re:CriticGPT: Finding GPT-4's mistakes with GPT-4 by phatfish on Thursday June 27, 2024 @04:18PM (#40814635)
Maybe fight fire with fire. Feed the ChatGPT PR to ChatGPT and ask it to do a review, paste that as the comment. It will even do the markdown for you!
[ Parent | on HN ]