Low-Level / Object-Oriented Design

A connected route from foundations to production systems: 3 stages and about 42 hours, including practice and projects. Learn, practise, and prove each stage.

Set a target
Your progress0 of 3 topics
Current stageInterfaces and invariants

Stage 1 of 3

Your paceNot set

Set a target on the planner

Take the placement check (10 min)

Draft. This path has not been reviewed by a second person yet. Topic order, estimates and tasks may change.

Arrows run from a prerequisite to what it unlocks. Select a topic to open it.
Filled: doneHeavy outline: in progressDashed: waiting on a prerequisiteDotted: skipped

The list view has the same topics and works with any screen reader.

  1. Stage 1: Interfaces and invariants

    1 topics · 10 h · milestone: Model a deck of cards0 / 1
    Stage project and rubric

    Model a deck of cards. Specify invariants and write tests for an invalid transition.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • Every type states its invariant, and the public interface exposes nothing a caller does not need.
    • A test proves an invalid transition is refused and the object stays valid.
    • You explain one design you rejected and why.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  2. Stage 2: Changes of state

    1 topics · 16 h · milestone: Implement a parking allocation policy0 / 1
    Stage project and rubric

    Implement a parking allocation policy. Introduce a different policy without rewriting callers.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • A second policy is added without changing any caller.
    • Every resource taken is released, including on an error path, and a test shows it.
    • You explain who owns each object and when it ends.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

  3. Stage 3: Stateful components

    1 topics · 16 h · milestone: Design a bounded chat cache0 / 1
    Stage project and rubric

    Design a bounded chat cache. Demonstrate eviction, fan-out and a test for a concurrent state change.

    Use your own small service or a disposable local example. Score each criterion: 0 missing, 1 partial, 2 demonstrated.

    • Each component's contract is written down and tested on its own.
    • Eviction keeps the cache within its bound, and a test shows which item goes.
    • A concurrent state change is tested repeatably, not by luck.

    Target: 2 on every criterion. Record your evidence in the notes of the stage's last topic. Report a problem with this project.

Source inventory and coverage

3 topics map to 6 unique activities. Shared resources count once. Every topic has a self-check; every stage has a project rubric.

Supplementary pages kept outside this path:

Pages under Library and Practice come from, or build on, Donne Martin's System Design Primer (CC BY 4.0).

Esc
↑ ↓ to move↵ to open