Wiki source code of Simple Design
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | Design should be as simple as possible. Only implement what's necessary for the current requirements. Simple code is faster to understand and easier to maintain. | ||
| 2 | |||
| 3 | ### Kent Beck's Rules | ||
| 4 | |||
| 5 | ... for simple designed code: | ||
| 6 | |||
| 7 | 1. **Tests Pass** | ||
| 8 | 1. **Reveals Intent** | ||
| 9 | * = Easy to read, self explanatory code | ||
| 10 | 1. **No Duplications** | ||
| 11 | * Sometimes simple abstractions are required, sometimes more complex refactorings or the introduction of design patterns. | ||
| 12 | 1. **Fewest elements** | ||
| 13 | * **Extra Code Means Extra Effort**: It increases potential bugs, maintenance, and developer cognitive load. | ||
| 14 | * **Lean Codebase**: Aim for a minimal set of elements. This is mainly about reducing unnecessary complexity, not just minimizing code. Minimal code is not always the easiest to understand. |