[golergka]

Your git strategy should depends on your business release cycle and priorities. In this case, it's a trade-off between dev branch stability and development speed.

With trunk-based development, everyone sees everyone else's work in progress and it's easier to integrate different features together. With feature branches, however, dev is more stable and there's more responsibility on merging to branch back to dev.

Are you deploying to public a few times a day like a web service, or are you working towards an early release, like a AAA game? Does your team sit together in one room, collaborating with one another, other do they take completely independent task and do them remotely, working from all across the globe, with the only point of interaction being a pull request once or twice a week?

It's impossible to say what's better or what's worse without these priors.