Comments by "Michael Stover" (@michaelrstover) on "Why The Hell Do You Still BRANCH?!" video.

Is this the first and only video you've watched from the channel??
7
@ContinuousDelivery I think the world of software engineering needs an answer to this question that isn't "Pair Programming". It's nice to be able to do pair programming, but if it comes across as the only way to make TBD work, then that in itself is pretty good justification for doing feature branching.
3
@ContinuousDelivery Because too many places won't do pair programming. Because too many developers don't enjoy doing pair programming. If it's honestly THE ONE AND ONLY WAY to do TBD, then that should be honestly acknowledged. I don't see that acknowledgement, and I personally don't think pair programming is the one and only way to do TBD, but I am not a central figure in the debate the way you are. I have always wanted to know how YOU would TBD without pair programming - but it's starting to seem like you wouldn't?
2
@alfbarbolani The studies done by the State of DevOps Report folks covers a lot of different teams, so you're arguing against real empirical evidence with little more than bald assertion based on personal anecdotal experience. It's fine to still prefer feature branching, but you should acknowledge the reality of the evidence stacked against you.
2