"Don't branch" was the hardest culture shift for me at Etsy. I'm still trying to figure out when it's appropriate. https://secure.phabricator.com/book/phabflavor/article/recommendations_on_branching/ …
-
-
@avibryant no, it works with a small team if you coordinate -
@bgreenlee@avibryant - I actually think the Etsy philosophy is better understood as “branch in code” rather than “no branches”. -
@rafeco@avibryant@bgreenlee A (domain-specific?) git successor could have native support for branches in code. Exciting thought. -
@lsinger@rafeco@bgreenlee I've also wondered idly about allocating traffic to branches instead of using flags. But unworkable I think. -
@avibryant@lsinger@rafeco@bgreenlee More concurrent experiments -> combinatorial explosion in branches. Fine for A/B testing, though.
End of conversation
New conversation -
-
-
@avibryant@bgreenlee The thing is: at a certain point you need feature switches anyway. Once you have that, you don't need feature branches -
@jasoncrawford@bgreenlee but there are things you can't feature flag. How do you coordinate, eg, an upgrade to a new version of a library? -
@avibryant@bgreenlee Good point. You can flag/switch on back-end changes sometimes, like API/schema changes. Library upgrade might be hard
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.