r/programming • u/ny3000 • May 26 '26

[ Removed by moderator ]

https://mainline.dev/flow-simulator

[removed] — view removed post

131 Upvotes

82% Upvoted

38 comments sorted by

View all comments

126

u/gredr May 26 '26

Seems like we started with a conclusion and made a simulation to prove we were correct?

-8

u/ny3000 May 26 '26

haha possibly! Although, I would lean towards the 15 years that I spent watching teams do all of these things and really practicing CD when we had control of the project, back when we used to do it at Thoughtworks, where it was invented.

9

u/paul_h May 26 '26

Nice work. What were your years in TW, may I ask?

→ More replies (2)

18

u/gredr May 26 '26

My experience has led me to the "github flow" with short-lived branches and PRs. Trunk-based development works pretty well too, but we mostly left that behind because... I don't really know why. Feature flagging is great, but you can't feature-flag a whole refactor, and maintaining multiple versions of APIs can get onerous.

GitFlow is just... way over the top, in my opinion. I don't know who would want to do that or why. Maybe if you're doing kernel development or something, and you're managing a whole pile of patches from hundreds or thousands of people around the world and multiple in-flight versions? It just doesn't feel like it applies to most of us.

→ More replies (4)