Do We Still Need Pipelines as Models Get Smarter?

early_burp · reddit · 2026-07-14

The author reviews their multi-stage Claude Code workflow: specification, planning, pre-execution validation, phased execution, automated review, and issue triage. In the past, these steps effectively caught unvalidated package versions, vague acceptance criteria, and massive changes lacking checkpoints.

During a real-world Flutter rewrite task, they found they could directly accomplish many pipeline-dependent steps through normal conversation: the model proactively asked clarifying questions, checked legacy compatibility formats, and automatically ran tests. The author's takeaway is that much of the harness was compensating for earlier model shortcomings, which are disappearing with each new version.

However, they emphasize that pipelines remain essential for quality-critical, deterministic steps. For instance, cryptographic compatibility has only one correct output and cannot rely on "the model is probably right." Once engineering discipline is codified into processes, what used to be a moat for senior engineers is being absorbed by the model.

Finally, they pose a question: are others also quietly trimming their agent harnesses? Which steps are genuinely useful, and which are merely compensating for model weaknesses?

Original post →

More from coding & agent

coding & agent channel →