Writing software is interesting. At one level, we write code to build a product, solve problems and make our lives easier. Whilst we’re building a product, we need to communicate to current and future selves and team members about what we’re doing and how our code works. Some of this communication is directly in code. Our function names, our variable names, our class names, our comments, and the list goes on.

Git Practices This is a summary of some common things you might need to look up, or things I might forget. Branches I like to use short lived branches and I’m the one who’s responsible for it. I’d suggest you do the same. It helps reduce potential issues when someone needs to re-write git history in a branch. But be warned. replacing git history is dangerous. It can cause others confusion.