Level 2 of 7 · about 1 week
Design principles
The rules that tell good classes from bad ones: SOLID, coupling, cohesion and when to keep things simple.
Modules
Core: everyone needs it. Common: most jobs use it. Specialist: optional depth, safe to skip on a first read.
1
2
Open for extension, closed for change
Add new behaviour without editing code that already works
Core 7 parts · about 3 hours
3
4
5
Depend on abstractions
Let important code point at interfaces, not at details that change
Core 6 parts · about 3 hours
6
7
DRY, KISS and YAGNI
Do not repeat yourself, keep it simple, and do not build what nobody asked for
Common 6 parts · about 2 hours