Commit your work daily, even if it's a WIP. Push it to the server. Open a pull request. Don't be afraid of sharing your incomplete work.

Every refactoring tends to entangle all the other functional changes together, which makes it even harder to advance changes to the production branch.

Feature flags are often misunderstood to be for front ends only. It is very possible to put all development behind a flag.

Several software delivery principles are widely applicable, beyond the strict definition of "software".

If you practice TBD with days-long branches, is it still TBD? I don't know. But it's certainly not continuous integration.

There are two related practices that are often called "Trunk-Based Development", which can lead to some confusion.

Are things moving slowly, but you don't know why? Reduce your batch size.

Lines of communication go up as team size increases, but that's not all. Consider merge conflicts.

Push to your staging branch as needed, but don't make it a mandatory step toward production.

A team I recently started working with has been using GitFlow. Until last week.

We natrually postpone painful experiences, but if we do them more often we're incentivized to reduce the pain.