2 ms·
Simple answer, no. If you're using if/else all over the place instead of a branch, what's to stop you from forgetting to remove one when you decide your new wo
by oxalo 12y ago
Simple answer, no.
If you're using if/else all over the place instead of a branch, what's to stop you from forgetting to remove one when you decide your new work is 'production ready'?
At the easiest level, I'd suggest using branches for new development. Bug fixes, new features, etc. Keep the work small; branches are cheap. Once its reviewed or tested merge it back into the master branch. This way 'in development' and 'complete' are abstracted to a level above code.
Also, imagine your project has 30 developers, or more. Would the strategy of if/else everywhere still work well?
- tylermauthe 12y agoThanks a lot for this answer. Good point about keeping the branches small and about having only two. The team I work on is quite small, so I can see how not using branches can work. I've worked on larger teams and I can't imagine how we would have managed those changes without an excellent branching model (git-flow).
- oxalo 12y agoAnd that's the other thing: use what works for your team. If you have an idea on how to make it better, try it. If something isn't working well, change it.