Re:Branchless development
by ianamartin on Sunday July 19, 2015 @09:46AM
(#9911171)
That's a funny saying. I have a very different saying. It goes like this: "It's always better to be correct than consistent."
Re:Branchless development
by 4lejandrito on Sunday July 19, 2015 @02:39PM
(#9912303)
I will give you another one:
When in Rome do as the Romans.
I think consistency is a best practice with precedence over all the other ones. Having a team agreeing on something and being happy with it is sometimes far more important than that something being the best of the possible choices.
Re:Branchless development
by jacques_chester on Sunday July 19, 2015 @10:04PM
(#9913698)
Let me expand.
The perfect is the enemy of the good.
It's unethical for me to put my own standard of perfection ahead of delivering business value and soundly engineered software.
My peers have opinions, formed validly, from their experiences. I have my own. Sometimes they differ. Sometimes I just need to suck that up and get on with the job.
That said, I'm anchoring a project where my predecessors chose a feature-branch model. I have a motto that "sometimes it's better to be consistent than correct". Done properly, it's not too hard, but in practice that's because we don't have a large team and we still rebase on and merge back to master frequently.