@avibryant I use feature branches all the time and am doing my best to spread the gospel.
-
-
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 Feature flags are also often incompatible with "leaving code better than you found it".1 reply 1 retweet 2 likes -
Replying to @dhh
@dhh@davidascher@avibryant@bgreenlee improving code merely for tightness sake is incompatible with having a scaled team3 replies 0 retweets 2 likes -
Replying to @kellan
@kellan@davidascher@avibryant@bgreenlee Sounds like you've given up on code quality. There lies the path to ruin.6 replies 1 retweet 4 likes -
Replying to @dhh
@dhh@kellan@davidascher@avibryant@bgreenlee Nonsense, you just release cleaner code behind ... a feature flag! And rampup finding bugs3 replies 0 retweets 1 like -
Replying to @mcfunley
@dhh@kellan@davidascher@avibryant@bgreenlee can you guys stop engaging@mcfunley he's tweeting all agitatedly during our vacation1 reply 0 retweets 10 likes
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.