Construction practice
How to write code that people can read and change.
- Naming
- Readable code
- Comments and documentation in code
- Code style and formatting
- Code smells
- Refactoring
- Code review
- Technical debt
- Defensive programming
- Working with legacy code
- Pair and mob programming
This area has no pages yet. The coverage plan lists the pages that it needs. You can write one of them. Read how to contribute.