> You have to understand how it is implemented under the covers. That's exactly the point the author was trying to make. Make Git so abstracted from the underl

> You have to understand how it is implemented under the covers. That's exactly the point the author was trying to make. Make Git so abstracted from the underlying tech it comparable to a simple task as editing a Google doc. > If this is your use case, then git is not for you. Well google docs can't have testing, it can't have merging as it is inherently "merged" already, etc. so totally not the use case the author was referring to.