Make your version control commits descriptive

It take a few more seconds to evaluate the update that has been made and describe it properly in a code commit message but it’s worth it. Take the extra time. I always regret when I’m lazy and just write “lots of updates.” Having a git repository shows you the history of your work and labeling your work is a short investment that will help you down the road.

This type of discipline in version control note taking ought to also be applied to general note taking about anything. If our notes aren’t organized about a topic, if they’re a mess, we’ll have a mess of a time trying to make them useful later. If they are neat then they’ll serve their purpose: To help us remember.

Notes and version control commit messages should work to help us simplify complexity but only if we take the time to write them properly.