Skip to content
AFTER CERTAINTY

Practice · Software engineers

After Certainty for Software Engineers

Coupling, feedback, and abstraction for people who ship systems—when technical judgment is collective and consequences are distributed.

Software engineers inherit the same tensions as any institution: weak feedback, tight coupling, and the temptation to substitute metrics for understanding.

The path

4 required stops · ~43 min · intermediate depth · primary book: Coupling

  1. Stop 1 of 4Concept

    Coupling

    Begin with coupling—how tightly joined parts of a system are, and what that means when something changes or fails.

  2. Stop 2 of 4Book

    Coupling

    The primary book on seeing where systems are joined, where they drift, and how those choices shape accountability.

  3. Stop 3 of 4Pattern

    Feedback Drives Change

    Notice when feedback loops actually change behavior—and when they are too slow, too noisy, or routed to the wrong people.

  4. Stop 4 of 4Concept

    Abstraction

    End with abstraction—what gets hidden, what gets simplified, and what judgment must still carry across layers.

Where this path leads

Technical judgment is never only technical. Coupling, feedback, and abstraction are ways of seeing how your work connects to everyone else's—and what breaks when those connections are misread.

Follow Judgment Before Certainty for the broader practice of acting before certainty, or Systems That Cannot Correct Themselves for institutional drift.