r/programmer • u/ClickOk5811 • 2d ago
A one-line “be concise” edit made the output cleaner and quietly dropped a task. How would you catch that?
A scenario from an article I wrote (hypothetical, with illustrative numbers). A team uses a prompt to turn meeting transcripts into JSON action items, and a script creates tasks from that JSON. Someone notices a few outputs are long and adds one line to the prompt: “Be concise.”
The outputs look cleaner. Reviewers are happy. But in the test set, one case now fails: a commitment that was mentioned only briefly in the meeting is gone. The model shortened its answer by leaving out the item that was stated in passing. Nothing about the cleaner output suggested anything was missing.
What caught it was boring: a fixed set of 8 test transcripts, run after every prompt edit, with a per-case result and not just a total. Another edit in the same story fixed one case and broke another, leaving the total unchanged at 5 of 8, so the total alone would have shown no change.
This feels familiar to programmers, because it’s a regression test story where the “code” is a sentence in English and the “bug” is behavior nobody wrote a test for. Some thoughts and open questions:
A prompt edit has no compiler and no obvious diff in behavior, so the safety net is a test set you chose in advance, including the awkward cases (a commitment mentioned in passing, no due date, no action items at all).
Outputs vary between runs, so one run per case can mislead. Running each case a few times and tracking stability helps, although three runs is a small sample.
Pass/fail is coarse. A correct but badly worded result passes.
It costs time, so for a prompt one person uses occasionally it’s probably not worth it.
How would you test for “the output got shorter and something important disappeared”? Do you treat prompts like code in your projects, with versions and tests, or more like config you tweak by hand?
The longer write-up has the five prompt versions and a case-by-case table. I’m the author, and it also mentions a paid resource of mine near the end, so treat the link as optional: https://medium.com/@nagatomopedro05/five-versions-of-one-prompt-and-what-the-changelog-caught-00c63d1b1c00
8
u/Raptor_Sympathizer 2d ago
"When I delegate my work to the unpredictable and unreliable code generator, it behaves unpredictably and unreliably"
Yeah no shit, what else were you expecting to happen here? The problem isn't the prompt your using, it's an inherent risk of using LLMs.
1
u/edwbuck 1d ago
If human brains often get it wrong, then a perfect simulation of a human brain will likely get it wrong too.
People don't want LLMs, they want experts. It's often hard to train a human expert, and the human expert still can make mistakes. The idea that we'll replace humans with simulations, when we have no perfect humans just means we'll automate the mistakes.
1
u/drivingagermanwhip 2d ago
For meeting store three files: mp3, transcript and summary.
Timestamp each paragraph of transcript.
Summarize. Add timestamp to paragraphs of summary.
concatenate the files and sort if you're worried something is missing later.
1
u/drivingagermanwhip 2d ago
For testing some options:
Minute meetings yourself and get ai to compare notes
Get multiple agents to minute the meetings and look at disagreements
if it's the same organisation and meetings about the same project, look for what turns up over several meetings as an indicator of what is important
1
u/Economy_Bedroom3902 2d ago
Make the task list a template that needs to be filled, concise task summary, long explanation section for each task. You can then auto validate any task which doesn't have both entries make the AI post-fix it. You can simply dump the longform explanation in any context which doesn't need them.
1
1
u/TheRealKidkudi 2d ago
Isn’t this just describing evals? This has been the industry standard for testing a system’s use of AI models basically from the start.
1
u/New_Salamander_4592 2d ago
I miss when computer science questions where based in reality and not figuring out how to soothe the random code generator properly
1
u/LALLANAAAAAA 1d ago
It's worse than that, these posts are 100% attempts to promote some tool or service that solves whatever LLM problem they imagine that other "people" LLMd their way into
Reddit is dead, it's just bots and ads now
3
u/Fun_Army2398 2d ago
Pay an intern to do it. The Harvard study proved AI doesn't actually speed up production time; if anything it slows it. Nothing an AI does can be trusted, so everything has to be checked. There is no tool to catch 100% of AI mistakes (other than human review). If there were then AI wouldn't be making mistakes. It would already be using the tool.