4 ms·
If the devs are experienced and you have confidence in tests, I like the trunk based approach WITH pair programming. Pairing takes care of review, testing ensur
by mping 7y ago
If the devs are experienced and you have confidence in tests, I like the trunk based approach WITH pair programming. Pairing takes care of review, testing ensures functionality and trunk based facilitates CD. If it is an internal project it's even better because the cost of a bug tends to be lower than public projects.
- shoo 7y ago> If it is an internal project it's even better because the cost of a bug tends to be lower than public projects. By this, do you mean that trunk-based development with pairing has a higher rate of shipping defects to production than other approaches? If so -- what's the upside of this approach?
- mping 7y agoI mean if you are inexperienced the risk is lower.