🔄Adapt's New Code Workflow: Build Wide, Demo Early
Build wide, demo early — a new code workflow
TL;DR
Adapt introduces a novel approach to coding where developers build wide and demonstrate features before committing any code. This shift aims to improve product validation and reduce big-bang merges.
Adapt has introduced a new workflow that flips the traditional model on its head: instead of writing an RFC, splitting it into issues, building each issue, and merging them in one go, developers now build wide, commit save points as they go, and demo features before anyone reads a line of code. This approach makes product validation faster by having the whole feature working early enough to show stakeholders. The key change is that while design still comes first, building happens broadly across components rather than in isolation. Code reviews remain unchanged but are more efficient due to smaller, focused PRs that flow through quickly, unlike heavy backend PRs which carry architectural risks and sit longer. This new method also emphasizes the importance of real dependencies when stacking work and ensures cleanup tasks ship last. The workflow includes grilling the plan until it has clear decisions, committing specs before coding begins, and managing splits based on what the code reveals during building. At Adapt, agents with business context from previous projects comment on reviews to ensure alignment.
Key Points
Design comes first, followed by building wide across components (not isolated issues).
Code reviews remain unchanged but smaller PRs flow faster, unlike heavy backend ones which carry architectural risks.
Stack only when dependencies are real; cleanup tasks ship last to avoid unnecessary work.
Agents with business context from previous projects comment on code reviews for alignment.
The workflow includes grilling the plan until it has clear decisions before coding begins.
Why It Matters
If you're working in a team that struggles with big-bang merges and delayed product validation, Adapt's new approach might be worth exploring. By building wide and demonstrating features early, teams can speed up development cycles without sacrificing code quality or architectural integrity.
Frequently Asked Questions
Why does this matter?
If you're working in a team that struggles with big-bang merges and delayed product validation, Adapt's new approach might be worth exploring. By building wide and demonstrating features early, teams can speed up development cycles without sacrificing code quality or architectural integrity.
What happened?
Adapt introduces a novel approach to coding where developers build wide and demonstrate features before committing any code. This shift aims to improve product validation and reduce big-bang merges.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 2,950 builders reading daily.