[dgb23]

I think it’s quite a reasonable method. But there’s no one size fits all.

Advocates of methodology will often speak in absolute terms. Plus their way of doing thinks is sometimes presented as a big magical revelation. This article is actually not like that, it reads like a historical summary.

It’s of course good to sometimes think about other ways of doing things. But in the end the way you’re using version control should reflect your requirements and development practice and not the other way around.

We do 1 main branch plus tagging. That’s it. It’s simpler for us and it’s a motivator to write code that works _now_.

But if we ended up in feature flag hell we would probably reconsider or simply branch off. Just be pragmatic about it.

There are of course companies with predefined rules about these things. I can’t speak to that.