HI version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
58% Positive
Analyzed from 466 words in the discussion.
Trending Topics
#model#code#sometimes#seem#prompt#each#ways#more#problem#output

Discussion (8 Comments)Read Original on HackerNews
The additional prompting doesn't necessarily need to tell the model specifically what to fix or do better, sometimes it's just enough to break it out of its habit. Asking for a smart looking, middle aged pelican on a sporty red bike isn't making the problem easier but does break it out of its boring defaults.
I wouldn't go so far as to say PEBKAC but the good news is there's still a role for humans in the loop.
It doesn't seem to depend on what model they use or how they prompt it. In code, there seems to be a loose correlation with testing styles; I've previously noticed that some people write tests to show that the code works as intended, and others try to write tests to show that it can't fail in ways that were unintended. But that correlation is weak.
I'm really puzzled by this.
I mostly use it for boilerplate code nowadays. Anything more complicated and it takes me more effort to review the output than to just code it slowly
It kinda feels like Michigan J Claude sometimes.
I wonder how long it will take to fix the quirks?
This will get sorted out in time and in the meantime, instruct the LLM away from averaged answers. It’s not a problem.
If you do not want images that have that instantly recognizable AI style to them - busy, perfect, bright colors pseudo realistic, outside what humans would usually make - then instruct the AI that such images are a failure to meet your goals and instead instruct them in other directions.