4 ms·
> Many teams don't do continuous integration. They have branches over branches over branches. There are many changes that are not in prod. Continuous integratio
by hu3 5y ago
> Many teams don't do continuous integration. They have branches over branches over branches. There are many changes that are not in prod. Continuous integration is about integrating several times a day. David Farley frequently talks about this. https://www.youtube.com/watch?v=Xl62gQpAl1w https://www.youtube.com/watch?v=Xl62gQpAl1w
Preach. As a consultant, I have been trying to implement continuous integration in a team and it has been so hard to convince project owners that delivering frequently and continuously to production behind feature flags is a net gain over accumulating "features" in dozens of branches that get outdated, poorly documented and even forgotten.
Some days the team crawls to snail pace trying to pick arbitrary branches to merge into integration branch. Then it takes days to be tested, adjusted, approved and merged into master. The process is so convoluted and cognitively loaded that it has been a major source of bugs.
They need better tests and continuous integration to become nimble.
- corpMaverick 5y agoYes. I have encounter similar behaviors in several places already.