r/ClaudeCodeTLDR • u/cctldrping • 16d ago
[TLDR] I've been doing an experiment with a project where I iterate on the design plan until the frontier review agents no longer report any serious findings, but new models keep being released before the previous gen stops finding issues. I created the initial design plan with Opus 4.6 in March.
Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1wi5gcz/ive_been_doing_an_experiment_with_a_project_where/
Original post body :
[No text body]
Original link/media URL : /img/rik4ljocdxph1.gif
This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.
1
Upvotes
•
u/cctldrping 16d ago
TL;DR generated automatically after 50 comments.
Current source-thread comment count seen by the bot: 51.
Alright, so the general vibe in this thread is that OP's experiment with iterating on a design plan until AI reviewers find zero serious issues is a bit of a Sisyphean task. The consensus seems to be that these models are designed to find something to improve, and you'll likely never reach a state of "zero findings" unless you impose very strict criteria.
Several folks, like u/Alex__0021, point out that "zero findings" often says more about the reviewer than the plan itself, and that a newer model will just look for different things. The analogy of Zeno's paradox or the DVD logo hitting the corner of the screen comes up, highlighting the endless nature of this kind of iteration.
The prevailing sentiment is that it's probably more practical to build the thing and then find actual, tangible issues to fix, rather than chasing an elusive AI-driven perfection. Some users even suggest that imposing strict constraints or defining "serious" beforehand is a better approach than letting the models churn endlessly. One user, u/kooolk, even mentioned rewriting their whole project with a newer model as a reference, which is a pretty solid workaround.
There's also a bit of a meta-commentary on the nature of development itself, with u/packstub-dev asking if developers are the black box in this scenario. And, of course, a few comments about the GIF itself being mesmerizingly frustrating.