Earlier quoted context omitted.
By now, a few years after ChatGPT released, I don't think anyone is thinking AI is objective and right, all users have seen at least one instance of hallucination and simply being wrong.
Sorry I can think of so many counter examples. I also detect a lot of “well it hallucinates about subject X (that the person knows well, so can spot the hallucination)” but continue to trust it on subjects Y and Z (which the person knows less well so can’t spot the hallucinations). YMMV.
LLMs work best when the user defines their acceptance criteria first
281–290 of 460 posts
Re: LLMs work best when the user defines their acceptance criteria first
#282Oftentimes, plausible code is good enough, hence why people keep using AI to generate code. This is a distinction without a difference.
Re: LLMs work best when the user defines their acceptance criteria first
#283Ok, I’ll bite: how is that different from humans?
It’s not. LLMs are just averaging their internet snapshot, after all. But people want an AI that is objective and right. HN is where people who know the distinction hang out, but it’s not what the layperson things they are getting when they use this miraculous super hyped tool that everybody is raving about?
Re: LLMs work best when the user defines their acceptance criteria first
#284Oftentimes, plausible code is good enough, hence why people keep using AI to generate code. This is a distinction without a difference.
There appears to be a similar approach in UX... plausible user experience is close enough.
Re: LLMs work best when the user defines their acceptance criteria first
#285Does it work if you get the agent to throw away all of its actual implementation and start again from scratch, keeping all the learning and tests and feedback? Gemini seems to try to get a lot of information upfront with questions and plans but people are famously bad at knowing what they want. Maybe it should build a series of prototypes and spikes to check? If making code is cheap then why not?
What I've found when doing exactly this, is that the cost of the initial code makes me hesitant to throw it away. A better workflow I've been using is instead to iterate on very detailed planning documents written in markdown and repeatedly iterating on that instead (like, sometimes 50+ times for a complex app). It's really quite amazing how much that helps. It can lead to a design doc that is good enough that I can turn the agent loose on implementation and get decent results. Best results are still with guidance throughout, but I have never once regretted hammering out a very detailed planning document. I have many times regretted keeping code (or throwing code away).
Re: LLMs work best when the user defines their acceptance criteria first
#286Ok, I’ll bite: how is that different from humans?
Human behaviour is goal-directed because humans have executive function. When you turn off executive function by going to sleep, your brain will spit out dreams. Dream logic is famous for being plausible but unhinged. I have the feeling that LLMs are effectively running on dream logic, and everything we've done to make them reason properly is insufficient to bring them up to human level.
Re: LLMs work best when the user defines their acceptance criteria first
#287Earlier quoted context omitted.
You're holding it wrong. Set the boundaries and guidelines before it starts working. Don't leave it space to do things you don't understand. ie: enforce conventions, set specific and measurable/verifiable goals, define skeletons of the resulting solutions if you want/can. To give an example. I do a lot of image similarity stuff and I wanted to test the Redis VectorSet stuff when it was still in beta and the PHP exten…
They aren't holding it wrong, it's a fundamental limitation of not writing the code yourself . You can make it easier to understand later when you review it, but you still need to put in that effort.
All the old techniques and concepts still apply.
Re: LLMs work best when the user defines their acceptance criteria first
#288Oftentimes, plausible code is good enough, hence why people keep using AI to generate code. This is a distinction without a difference.
No. Plausible code is syntactically-correct BS disguised as a solution, hiding a countless amount of weird semantic behaviours, invariants and edge cases. It doesn't reflect a natural and common-sense thought process that a human may follow. It's a jumble of badly-joined patterns with no integral sense of how they fit together in the larger conceptual picture.
Re: LLMs work best when the user defines their acceptance criteria first
#289Ok, I’ll bite: how is that different from humans?
It’s not. LLMs are just averaging their internet snapshot, after all. But people want an AI that is objective and right. HN is where people who know the distinction hang out, but it’s not what the layperson things they are getting when they use this miraculous super hyped tool that everybody is raving about?
Re: LLMs work best when the user defines their acceptance criteria first
#290Earlier quoted context omitted.
It’s not. LLMs are just averaging their internet snapshot, after all. But people want an AI that is objective and right. HN is where people who know the distinction hang out, but it’s not what the layperson things they are getting when they use this miraculous super hyped tool that everybody is raving about?
The etiquette, even at the bigtech place I work, has changed so quickly. The idea that it would be _embarrassing_ to send a code review with obvious or even subtle errors is disappearing. More work is being put on the reviewer. Which might even be fine if we made the further change that _credit goes to the reviewer_. But if anything we're heading in the opposite direction, lines of code pumped out as the criterion of…