DEV SAGA

Phase 3-4 · Chapter IX · World 3, Design Plateau · Case

Software architecture

What to study in Software architecture, in this order: 4 books from first step to reference, 5 AI skills to use at work and the people worth following.

Reading path, in order

  1. 1. Start hereFundamentals of Software ArchitectureMark Richards, Neal FordSee on Amazon
  2. 2. Go deeperClean ArchitectureRobert C. MartinSee on Amazon
  3. 3. Go deeperSoftware Architecture: The Hard PartsNeal Ford et al.See on Amazon
  4. 4. ReferenceBuilding Evolutionary ArchitecturesNeal Ford, Rebecca Parsons, Patrick KuaSee on Amazon

AI skills for everyday work

/decision-record

Architecture decisions nobody remembers the reason for.

  • Turns a discussion into an architecture decision record (ADR)
  • Makes the discarded alternatives and the trade-offs explicit
  • Asks what moves elsewhere because of the decision
  • Separates reversible decisions from irreversible ones

How to ask: Use the skill decision-record on yesterday's discussion about queues.

/explicit-tradeoff

Architecture choices defended by taste, not by consequence.

  • Compares two or three options side by side
  • States what each one gains, what it loses and what moves elsewhere
  • Points out the cost of reversing each choice
  • Ends with a recommendation and the explicit downside

How to ask: Use the skill explicit-tradeoff to choose between a queue and a synchronous call for the invoicing service.

/c4-diagrams

Architecture that only exists in the head of whoever designed it.

  • Reads the code or the system description
  • Generates the context, container and component diagrams
  • Includes a legend and an element table
  • Says which diagrams are not worth it for this case

How to ask: Use the skill c4-diagrams on this repository for Friday's presentation.

/coupling-and-cohesion

Modules that always change together and dependencies that go in circles.

  • Maps the dependencies between modules
  • Points out cycles and modules that depend on everything
  • Shows which files change together in the git history
  • Suggests where to draw the boundaries

How to ask: Use the skill coupling-and-cohesion on the billing monolith.

/architecture-rules

The agreed design that the code forgets within six months.

  • Turns architecture decisions into automated tests
  • Detects when the code drifts away from the design
  • Runs in the pipeline and fails the build on a violation
  • Links each rule to the decision (ADR) behind it

How to ask: Use the skill architecture-rules for the layers of the order service.

Who to follow

Play this phase on the map

Dev Saga is a pixel-art world map with the 30 phases of the journey to Staff Engineer. Track what you read and used, on your own or with a book club, and export your progress to show your leadership.

Open phase 3-4 on the map Bring it to my team