Names: Use clear, searchable, and pronounceable names for variables, functions, etc. to make code easier to understand and maintain.
Functions: Keep functions small, focused on one task, with few arguments and no side effects. Use descriptive names and separate commands from queries.
Comments: Avoid relying on comments to clarify unclear code. Instead, strive for clean, understandable code.
Error Handling: Treat error handling separately from regular code. Use exceptions instead of return codes and provide context with exceptions.
Formatting: Maintain consistent code formatting for readability. Teams should agree on a single style.
https://bookpecker.com/
Names: Use clear, searchable, and pronounceable names for variables, functions, etc. to make code easier to understand and maintain.
Functions: Keep functions small, focused on one task, with few arguments and no side effects. Use descriptive names and separate commands from queries.
Comments: Avoid relying on comments to clarify unclear code. Instead, strive for clean, understandable code.
Error Handling: Treat error handling separately from regular code. Use exceptions instead of return codes and provide context with exceptions.
Formatting: Maintain consistent code formatting for readability. Teams should agree on a single style.