The document discusses best practices for source control including committing code frequently, writing detailed commit messages, and following a good development process of getting up-to-date, building, testing locally, and committing changes. Anti-patterns for commit messages like vague messages without details are also highlighted.
21. Here are some anti-patterns of good commit messages:
1. Some shit.
2. It works!
3. fix some fucking errors
4. fix
5. Fixed a little bug...
6. Updated
7. typo
8. Revision 1024!!
22.
23.
24.
25. Good process:
1. Get up-to-date
2. Build
3. Never work on broken build
4. Develop
5. Build
6. Local testing
7. Commit
8. Resolve conflicts immediately
9. Get up-to-date