[nottoohard]

Hey, so, these are not problems unique to git, for what it's worth. And if people don't want to deal with problems, then maybe software development isn't for them, because this is like a plumber complaining about joining pipes. (And don't bother belaboring this analogy, because I will not respond.)

[112233]

No, it's like plumber complaining about filling tax return forms. In the middle of joining pipes. (And I will bother belaboring your analogy. For the benefit of others reading it.)

As you say, it is not unique to git. Bug trackers, system updates etc. also can "disrupt flow" and take a lot of attention away from the main work. But git is unique in the insidious way that it springs such hard problems on unsuspecting developers that are busy *actually working*

[skydhash]

Git is there for tracking changes. If you don't care about that, then there's nothing to be done. If you do care about it and it's important for your job, you learn the tool and use it. And git is a good tool.

[112233]

Git is a good tool for tracking changes if your primary job is tracking changes. It is terrible tool if you care about tracking changes because you need your work done. There is no encapsulation and the cognitive load and amount of moving parts you need to keep track of mentally is hugely distracting.