[tawb]

My experience with git has been pretty limited to Github. I've been working on software for five years, and mostly full stack in small startup teams so I'm lacking some breadth of experience that I was hoping to find some more of on HN.

But a few things that have always stood out to me about the user experience of version control:

- Git allows us to work in parallel effectively on different branches, but when our whole team is focused on one set of interrelated new features, we spend a lot of overhead coordination time figuring out how to not create conflicts for eachother. So we can work in parallel, but not in real-time with eachother's changes. The multiplayer aspect of design in Figma comes to mind here.

- I and many folks at my level use github in much simpler way than many older coworkers do. I rarely touch anything that isn't basic branching, commits and merging

- As a very visual thinker, it took me a very long time to grok git and what I was doing. As I've worked with more devs who come from non-engineering backgrounds, I've found this pretty common

[andsoitis]

> when our whole team is focused on one set of interrelated new features, we spend a lot of overhead coordination time figuring out how to not create conflicts for eachother. So we can work in parallel, but not in real-time with eachother's changes

If multiple people work on the same code (interrelated new features) at the same time, it seems to me they would have to sequence their work (i.e. coordinate) so as to not step on each others' toes. Put differently, this sounds like the problem is inherent and won't be solved by technology.