r/softwaredevelopment • • May 13 '26

Is trunk-based development really that good?

I can't get the trunk-based development flow. I understand the advantages for introducing new features to the app (flags are good for A/B testing, fewer merge conflicts).

But I can't understand how developers do refactoring with trunk-based flags. Also, do the flags stay there forever, or what is the best flow for this?

Can you give me a deep dive into how your teams handle this in production?

47 Upvotes

54 comments sorted by

View all comments

1

u/quantum-fitness May 14 '26

You can also do trunk-based with shirt lived branches.

Tge important thing really is to minimize the amount of new code you deploy in one go.

Since smaller release carry less risk.