News for hackers. Stuff that matters.
Re:Why is git pull considered harmful? (2013) by lars on Wednesday March 12, 2014 @10:58AM (#7385940)
> But you can't actually 'work on the same code'. You have to have a copy.

Surely this is a little overly pedantic? The point is that you want developers A and B to work on code bases that are as close to each other as possible, so that any problem in the interaction between these developers' work is caught early. Your project doesn't need to be completed in a day or two, you just need to accept that you have a dev branch which isn't always in a shippable state (which I think is usually unproblematic).

Re:Why is git pull considered harmful? (2013) by JoeAltmaier on Wednesday March 12, 2014 @01:09PM (#7386856)
Which begs the question: which branch? How do you know what all the others are working on, and if you'll conflict.