Comments by "" (@adambickford8720) on "Why CI is BETTER Than Feature Branching" video.

@stojadinovicp That's just not true; this is not a silver bullet. Sometimes large frameworks break things with no 'intermediary' path, its all or nothing. For example, Spring R2DBC changed their DB client which broke every single one of our DAOs. The 2 clients can't co-exist so 'branching by abstraction' isn't really an option (this involves DB txns, so even stupid class loader tricks won't save you). Cybersecurity is demanding that upgrade, yet the team still has to deliver on the existing roadmap.
5
Taken to an extreme this would end up with the whole team 'live editing' the entire code base. Even if unit/integration test were instant (could theoretically create a deployment artifact on every keystroke) I don't think this would work w/o some kind of 'check pointing'? Where's the 'sweet spot'?
4
@JojOatXGME I meant it more as a thought experiment than anything.
1
@rosstempo3765 You clearly missed the point.
1
@rosstempo3765 I've been using git for a decade, this has NOTHING to do with technology. My question is 100% methodology based to the unrealistic degree that technology doesn't limit at all. Does 'stress testing' the idea fall down and where? Specifically, "if we could theoretically create a deployment artifact on every keystroke instantly". This implies its so continuously merged that the concept of a 'branch' is meaningless. I'm not convinced that's a good (manageable) thing.
1