Look I'll say this much: working on projects by myself lends well to branching. I can go off on a tangent, fiddle around with stuff, break it all, then decide if I want to merge or not and basically never worry about a conflict. Not 100% of the time but most of the time. Awesome.
But in a team, three or more, I can see the issue. It's not always just "Communicate more. That will fix all your problems". It's also about how other developers work through their process. That process doesn't always include committing code every day, for example. Can you consistently make everybody play ball with a set of rules you have to adhere to? Does putting handcuffs help the team or hinder? I'd say it's arguable.
You've got a lot of nerve posting something like this here. But good for you. That's what I think dev.to is about. You can post an opinion that's not popular and then debate it.
Look I'll say this much: working on projects by myself lends well to branching. I can go off on a tangent, fiddle around with stuff, break it all, then decide if I want to merge or not and basically never worry about a conflict. Not 100% of the time but most of the time. Awesome.
But in a team, three or more, I can see the issue. It's not always just "Communicate more. That will fix all your problems". It's also about how other developers work through their process. That process doesn't always include committing code every day, for example. Can you consistently make everybody play ball with a set of rules you have to adhere to? Does putting handcuffs help the team or hinder? I'd say it's arguable.
You've got a lot of nerve posting something like this here. But good for you. That's what I think dev.to is about. You can post an opinion that's not popular and then debate it.
Keep up the good work.
If the team can't play ball with the rules any system or technique would fail.