I found deeply interesting the resistance of software developers that yet haven't tried
#TBD (Trunk-Based-Development), and still resists to it. Here are some of the things that I observed when it happens:
1. It is preferred to have a complex branching model over following common and tested engineering practices to keep main stable -
#TDD, parallel change, feature flags and observability are examples that those teams lack
2. using pull requests are preferred to gate keep changes instead of work together (in pairs for instance) and spread good standards and evolve as a team. Pull requests are there just because of "company standards" and become check mark and the work is not reviewed at all
3. Integrating the work becomes delayed and preferred. Code merge conflicts are seen are usual, and big bang code changes are source of hours of fix conflicts.
in short: in an attempt to be "faster" instead of adapt to change, road blockers are put in place to avoid the smallest progress possible, usually it comes accompanied with the usage of
#SCRUM to some extend.
Teams are used to the big bang releases day that become a source of: worries and lack of confidence if it will work or not.