4 ms·

Sounds to me that we work for the same company :) I bought into feature branches and all that stuff right after uni and tried to apply it at my first job witho

Sounds to me that we work for the same company :) I bought into feature branches and all that stuff right after uni and tried to apply it at my first job without all the success I was expecting. Then when I moved to my current job in which we do TDD, Pair programming and single branch development I was a bit reluctant. After almost 2 years I haven't come up with a single scenario in which this approach has given us any troubles and in hindsight I think is what I should have proposed at my first job.

jacques_chester 11y ago
Until I got to Pivotal Labs, developing on a single branch seemed impossible. Now it seems obvious. 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.
- ianamartin 11y ago
  That's a funny saying. I have a very different saying. It goes like this: "It's always better to be correct than consistent."
  - 4lejandrito 11y ago
    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.
  - jacques_chester 11y ago
    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.

4 ms·

Sounds to me that we work for the same company :) I bought into feature branches and all that stuff right after uni and tried to apply it at my first job witho

by 4lejandrito 11y ago

jacques_chester 11y ago
Until I got to Pivotal Labs, developing on a single branch seemed impossible. Now it seems obvious. 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.
- ianamartin 11y ago
  That's a funny saying. I have a very different saying. It goes like this: "It's always better to be correct than consistent."
  - 4lejandrito 11y ago
    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.
  - jacques_chester 11y ago
    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.