> is “how Git implements it” really the right way to explain it? >> Of course not, As long as the user is a software developer I would disagree. If the develo

> is “how Git implements it” really the right way to explain it? >> Of course not, As long as the user is a software developer I would disagree. If the developer cannot understand the implementation concept style of explanation, I don't want to use or review their code either. I am saying implementation concepts as object storage, branches being pointers to objects etc. Of course implementation details and optimizations like packfiles don't matter. Every user-friendly explanation will have its limits once we get merges, rebases etc. For software developers it is important that their mental models don't hit such limits. If the user is not a software developer you have a point.