Software Engineering Is Becoming Plan and Review
summary
Claim: software engineers shift into plan-based vs review-heavy workflows as Copilot Claude Code and agent tooling (Codex Cool Code Playwright MCP) displace typing. Specific tradeoff: five minutes of upfront planning saves thirty minutes of review. Ops change when agents pass the five-minute agent threshold, driving parallelization and new interfaces like Vibe Kanban that run multiple agents concurrently. Evidence includes running agents with long executions, and a real project with 30,000 monthly active users and 25,000 GitHub stars that is being shut down.
AI-written summary · about
chapters (10)
- 0:00Intro and agenda
- 1:45Why software engineering is shifting to plan and review
- 3:30The two approaches: Plan-based vs. Review-heavy
- 6:02The matrix: Feature development vs. migrations and maintenance
- 7:27The impact of agent execution time
- 9:52Managing the 'five-minute' agent threshold
- 10:29Parallelization and workflow management
- 12:00Vision for future coding interfaces and 'focus maxing'
- 14:00Announcement: Shutting down Vibe Kanban
- 18:13Q&A: Next steps and reflections on the startup journey
related talks
51mFuture of Software Development
16mBeyond the IDE: The Future of Developing Software With Agents
46mAgentic Engineering: From Writing Code to Reviewing It
30mExperiments in Engineering without reading code
46mWhen You Run Out of Requirements: What Happens When You Go All-In on Agents
33mThe Autonomous Enterprise
25mBeyond the IDE: Toward Multi-Agent Orchestration
27mSoftware engineering with GenAI