How I Write Software with LLMs — Multi-Model Pipeline Hits 522pts/505cmts on HN

Stavros Korokithakis published the most practically useful LLM workflow post to date, and Hacker News responded with the highest engagement of the day: 522 points and 505 comments. The methodology: Claude Opus 4.6 as architect for deep feature planning, Claude Sonnet 4.6 as developer with narrow execution latitude, and independent models as cross-model reviewers to prevent groupthink.

The critical insight: "I no longer need to know how to write code correctly at all, but it's now massively more important to understand how to architect a system correctly." This reframes the skill shift — it's not "coding is dead," it's that the bottleneck moved from implementation to decomposition and specification.

The cross-model review step is the key differentiator from naive vibe coding. A 517-upvote r/ClaudeAI thread independently documented practitioners routing Claude's plans through ChatGPT Pro for adversarial review before executing — discovering meaningful revisions in a significant fraction of cases. The emerging pattern: Claude for generation, GPT for critique, then back to Claude for implementation.

This methodology sits at the exact midpoint between two failing approaches. Pure vibe coding — accept everything, understand nothing — produces the Vinext disaster. Pure skepticism — reject AI tooling entirely — leaves 6 months of backlog on the table while competitors clear it. The disciplined middle path — architect manually, delegate implementation, verify with adversarial cross-model review — is what actually works. Source