Re:Tokenmaxxing is dead, long live tokenmaxxing
by theanonymousone on Sunday June 28, 2026 @01:56PM
(#48709733)
What is meant by a "loop" here? Just repeating the same prompt until you get the desired result? Are subsequent repetitions too close to each other?
[ Parent
| on HN ]
Re:Tokenmaxxing is dead, long live tokenmaxxing
by untwerp on Sunday June 28, 2026 @04:05PM
(#48711042)
Loop "engineering" has now become a thing now apparently (a la prompt "engineering")
https://github.com/topics/loop-engineering
Re:Tokenmaxxing is dead, long live tokenmaxxing
by throwaway89201 on Sunday June 28, 2026 @02:18PM
(#48709939)
> Just repeating the same prompt until you get the desired result?
Not necessarily the desired result, but until it's 'done', where the LLM itself is the judge on if the is the case according to the given criteria (often just an updated todo-list). One of those extremely simple 'harnesses' (if you can even call it that) was even named the 'Ralph Wiggum Loop' [1] to allude to the braindead-but-persistent tokenmaxxing it results in.
Re:Tokenmaxxing is dead, long live tokenmaxxing
by SchemaLoad on Sunday June 28, 2026 @07:40PM
(#48712973)
What I have been doing seems a bit different to what's described, but I always make sure to define how to know the task is done so the agent doesn't quit early. Usually this means telling it to to run the tests and type checks to ensure it runs without errors.
Otherwise they often do a first pass looks good enough but it doesn't actually work.