I will jump right into the notes, the description for the note formatting is in the first post of this series
Chapter 5 - Formatting
- Good formatting is good for communication, and we should strive to have good communication
- Small files are better to understand (and therefore better to work with) when compared to big files
- Vertically close lines of code should have a close logical relation
Variables should be declared as close to their usage as possible
- Functions that are called by another function in the same file should be right below the caller
- Big lines of code are bad, 120 characters/line is fine, more than that is not
- The team has the final word on the formatting rules for the codebase
Top comments (0)