I couldn't disagree more. I've worked on teams using a single branch methodology and it was always a mess. I've had no problems at all with a feature-branching approach. You give a cute analogy with the painting but it doesn't really hold up in real life. Of course, there are organizational challenges with it as well, but nothing that isn't manageable. Working in feature branches on a single project is like different mechanics working on the same car. If one works on the exhaust while another is fixing the brakes, you're fine. If you ask both to do different tasks, both on the engine, then sure, you're gonna have problems. So... just don't.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I couldn't disagree more. I've worked on teams using a single branch methodology and it was always a mess. I've had no problems at all with a feature-branching approach. You give a cute analogy with the painting but it doesn't really hold up in real life. Of course, there are organizational challenges with it as well, but nothing that isn't manageable. Working in feature branches on a single project is like different mechanics working on the same car. If one works on the exhaust while another is fixing the brakes, you're fine. If you ask both to do different tasks, both on the engine, then sure, you're gonna have problems. So... just don't.