Git

Question 1

Why should you build novel length commit messages?

Answer 1

Commit messages should show WHY a change was made. Remember about the in-memory ordering caused by a default ordering in an ActiveRecord model that was removed after a while, but no one removed the in-memory ordering. https://vimeo.com/28AC0579162

Question 2

Should you use git commit -m

Answer 2

No, the command line is not the place to write long commit messages explaining why a change was made.

Question 3

What is better than git blame?

Answer 3

The pickaxe:

git log -S snippet_of_code

Question 4

What is important in a commit message?

Answer 4

Explaining the WHY

NOT the what

Question 5

Should you leave not valuable commits in history?

Answer 5

No, treat your commits as mutable. Use amend and rebase.