The trunk-based development debate started by @thorstenball has clearly touched a nerve. So I thought, why don't we look at some numbers?
I built a little simulator with the help of our dear colleague Opus to compare four different integration strategies:
1. Trunk-based development (@thorstenball's horse)
2. Merge queue as the only CI gate (what I'm currently using)
3. PR-based, requiring a fresh base
4. An agentic merge queue, with built-in conflict resolution (dream option, can't buy it anywhere yet)
You can play with the simulator here:
Learning
An interactive simulator for trunk-based development strategies
Luca Palmieri built an interactive simulator with Opus to compare trunk-based development, merge queues, PR-based flows, and an agentic merge queue with conflict resolution. The playable tool is linked in the post.
236likes
16reposts
376saves
38Kviews
- Made with
- Opus
- Role
- Rust / backend dev
- Posted
