3 ms·
You are mistaking the tools you use for the tools that a team can use. That's Git: it lets teammates communicate changes in a straightforward, consistent manner
by dexen 16y ago
You are mistaking the tools you use for the tools that a team can use. That's Git: it lets teammates communicate changes in a straightforward, consistent manner, with little overhead. With a tool suite to review, pull en mass or cherry-pick the changes at will; with the defaults being the most practical choices most of the time.
If you want your team to be more than a sum of the members (as opposed to stepping on each others' toes), you need decent communication tool.
Or you can dispose of communication by being a lone wolf.
- abyssknight 16y agoJust to play devil's advocate here, and definitely not disagreeing with you, but... Do you know how we communicated changes before git and other team tools? With our voices, markers, and boards. If your team steps on each other's toes, might that not be a problem with the team dynamics and not necessarily the tools themselves?
- danssig 16y agoThe easier you make things for people the less likely they are to mess it up. We used to get around by horse and buggy but I think you'd agree that a change in tools has been a benefit that lets us do things we couldn't do before, wouldn't because it was too hard or tried to do but failed often from the same mistakes over and over.
- dexen 16y agoThose are not the changes you are looking for :-) You are absolutely right about the way to propagate changes in ideas, prerequisites, protocols etc. etc.. Actually, I'm a frequent whiteboard user myself. I should've made myself clear I was meaning the physical changes to the implementation files; in any case, something that is byproduct of information shared verbally.