and the indent level should not be greater than one or two.
2. Do One Thing
- Functions should do one thing. They should do it well. They should do it only.
Steps of function are one level of abstraction below the name of the function. Then the function is doing one thing.
Another way to know function is doing more than one thing is if you can extract another function from it.
3. One level of abstraction per function
The stepdown rule - reading code from top to bottom.
4. Use Descriptive Names
Don't be afraid to make a name long.
A long descriptive name is better than a short magic name.
A long descriptive name is better than a long descriptive comment.
Dont't be afraid to spend time choosing a name.
Be consistent in your names.
5. Function Arguments
The ideal number of arguments for a function is zero.
Three arguments should be avoided.
Flag Arguments - can be split into two function.
Aruments Objects - group the variables and abstract concept if possible.
Verbs and keywords - function and argument should form a very nice verb/noun pair.
6. Have no side effects
7. Command Query Separation
- Functions should either do something or answer something, but not both.
8. Prefer Exceptions to returning error codes.
Extract try/catch blocks, error handling is one thing.
9. DRY - don't repeat yourself
- especially the duplicated logic.