Can anyone unpack this for me? https://twitter.com/rg9119/status/1327115846167064576?s=20 > <https://twitter.com/rg9119|Ron Garcia> > https://twitter.com/rg9119\|@rg9119 > > A student in my course taught me how https://twitter.com/racketlang\|@racketlang > can improve my version control experience:

It just commits all changed files with a ‘random enough’ commit message and pushes directly. Not exactly recommended :wink:

I don’t get why a random commit message is desirable?

I suppose it’s just to make sure they are distinct, but I’m not sure that’s necessary

(in particular since every commit has its own hash)

I know people who use "." as their commit message, and I don’t know why. Using "." probably raises fewer questions than “g880”.

I love people who enter informative commit messages…because I sometimes read them :100:

https://dhwthompson.com/2019/my-favourite-git-commit

Writing good commit messages and breaking down changes into coherent pieces is a fine art.