Follow-up · depth 2
What are common failure modes of Trunk-Based Development vs Long-Lived Branches?
What are common failure modes of Trunk-Based Development vs Long-Lived Branches?
Answers use simple, clear English.
Audio N/AQuick interview answer
Common failures around Trunk-Based Development vs Long-Lived Branches: blocking the hot path, ignoring backpressure, and weak timeout/retry design. Week-long feature branches without syncing main.
Detailed answer
Failure modes for Trunk-Based Development vs Long-Lived Branches: Known pitfalls: Week-long feature branches without syncing main. • Missing timeouts / unbounded retries • No backpressure when downstream slows • Assuming ordering/guarantees the runtime does not provide How seniors prevent them: Required checks; small PRs; flags for incomplete features. Parent context: Simple view: Short-lived branches merge to main frequently; feature flags hide incomplete work. Long-lived release branches increase merge pain and drift.
Full explanation
Name concrete failure modes and the mitigation for each — that scores higher than a vague “it can fail.” Short-lived branches merge to main frequently; feature flags hide incomplete work. Long-lived release branches increase merge pain and drift.
Follow-up questions
Only answered follow-ups are shown — click to open with full answers
Parent context — Trunk-Based Development vs Long-Lived Branches
Simple view: Short-lived branches merge to main frequently; feature flags hide incomplete work. Long-lived release branches increase merge pain and drift.
View full parent question →