Developer seeks feedback on AI-assisted feature development pipeline
A developer shared a detailed 5-step assembly line for feature development using AI, where each step requires passing a checklist before proceeding. The process includes spec writing, plan review, and multiple reviewer passes for risky features. The post asks whether this approach is efficient or wastes tokens.
Entities
Related
Developer shares practical AI coding workflow: paper first, then Fable/Opus for planning, Sonnet for implementation
A developer on Reddit outlines a structured AI-assisted coding workflow for full projects, emphasizing upfront planning on paper before involving any model. The pipeline uses Fable for planning, Fable/Opus to break work into markdown files, and Sonnet for implementation under a safety hook, contrasting with the common 'vibe coding in agent mode' approach.
Developer seeks ways to have AI improve existing features rather than suggest new ones
A developer with over a year of AI-assisted project building reports difficulty getting AI to suggest improvements on existing features instead of proposing new ones. They have tried asking the AI to scan a project directory but find it consistently veers toward new feature suggestions.
Founders advised to grade AI output rather than understand model internals
A Reddit post argues that founders should not delay shipping AI agents due to a need to understand the model's internals. Instead, they should build systematic evaluation pipelines that compare outputs against known correct answers and catch regressions before users see them.
Users share strategies to reduce iteration loops with Claude Code
A Reddit user describes a multi-step workflow to minimize back-and-forth with Claude Code for production-ready code, involving iterative plan refinement before code generation. The post highlights a common pain point of excessive iteration in AI-assisted coding.
Developer recounts AI-assisted coding pitfalls after building 4 products in 3 months
A developer built four products almost entirely with AI over three months. Three turned out fine, but one became an unmaintainable mess requiring a complete rewrite. The developer blames their own iterative prompting approach, which layered patches without architectural foresight, leading to a fragile codebase that neither they nor the AI could later fix.