"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/ …
-
-
Replying to @avibryant
@avibryant I use feature branches all the time and am doing my best to spread the gospel.2 replies 0 retweets 1 like -
Replying to @bgreenlee
@bgreenlee@avibryant the challenge is the use of branches requires sophisticated trade offs and the use of feature flags doesn't2 replies 0 retweets 1 like -
Replying to @kellan
@kellan@bgreenlee I'd like to hear more about that because it's not obvious to me.2 replies 0 retweets 1 like -
Replying to @avibryant
.
@kellan@bgreenlee no-branches feels to me like integration-cost insurance: you expect to pay more overall to avoid any catastrophic loss.2 replies 0 retweets 2 likes -
Replying to @avibryant
@avibryant@kellan@bgreenlee it's biasing towards making testing of small ∂ improvements easier at the cost of making large Δ much harder5 replies 2 retweets 2 likes -
Replying to @davidascher
@davidascher@avibryant@kellan@bgreenlee I don't think that's right. You just have to get more creative about how you deploy big changes.1 reply 0 retweets 0 likes -
Replying to @jasoncrawford
@jasoncrawford@davidascher@kellan@bgreenlee big changes are already hard and risky; making them even a little harder seems worrying.2 replies 0 retweets 0 likes -
Replying to @avibryant
@avibryant@davidascher@kellan@bgreenlee The way I see it is: you're making them a little harder in order to make them a lot less risky1 reply 0 retweets 0 likes
@jasoncrawford @davidascher @kellan @bgreenlee but make them hard enough and you massively increase the risk they won't even get attempted.
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.