CSE Roadmap

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. 1

    Single responsibility

    One class, one group of people who ask for changes

    Core 7 parts · about 3 hours

  2. 2

    Open for extension, closed for change

    Add new behaviour without editing code that already works

    Core 7 parts · about 3 hours

  3. 3

    Substitutability

    When a subclass can safely stand in for its parent

    Core 6 parts · about 3 hours

  4. 4

    Small interfaces

    Do not make a class depend on methods it never calls

    Common 6 parts · about 2 hours

  5. 5

    Depend on abstractions

    Let important code point at interfaces, not at details that change

    Core 6 parts · about 3 hours

  6. 6

    Coupling and cohesion

    Two measures of how well a design holds together

    Core 6 parts · about 3 hours

  7. 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