5 ms·
Is the problem that git is too hard or that the typical person’s mental model of collaborative development is too naïve?
by fiddlerwoaroof 3y ago
Is the problem that git is too hard or that the typical person’s mental model of collaborative development is too naïve?
- vjk800 3y agoAs I wrote in my other comment, typical person's mental model is centralized. They expect there to be only one, centralized source of truth for everything
- morelisp 3y agoThis is definitely the real question always underlying this topic, but maybe more charitably: how typical is a collaborative development experience vs. a single-step hierarchy with blessed releases? Is there really a practical argument to learn it, or only moral and aesthetic ones?
- fiddlerwoaroof 3y agoI don’t think of “naïve” being an uncharitable. It’s just the difference between the way a problem appears to someone unfamiliar with it to the model they form after they’ve worked it out.
- convolvatron 3y agohow about - gits model doesn't map very well into the workflows I use...so its always a struggle and source of conflict with other developers.
- dasil003 3y agoThat’s the beauty of git though. You can do any workflow you want locally (including with no internet) and slice and dice however you need to push your work back to the team.
- Gibbon1 3y agoMy impression is if you think in terms of it automating the process where developers email patches to Linus and his minors who then review and commit and merge it makes somewhat more sense.