Final Capstone Review

Introduction

Final capstone review closes the course tying every lesson together. Four projects demonstrated pattern composition. This lesson reflects on meta-skills: selection discipline, vocabulary fluency, design review communication, and removing abstractions — not just adding them.

The story

Staff engineer promotion review featured 3 named-pattern stories — checkout rebuild, payment gateway, multi-tenant migration. In each she emphasized patterns she removed that no longer earned their cost. Promotion granted.

The business problem

Engineers who only add patterns become architecture astronauts:

• Addition bias: promotion packets list patterns added, never removed.
• No selection framework: can't explain why not Factory.
• Vocabulary without stories: names patterns, no outcomes.
• Interview gap: can't compose patterns in system design.

The problem teams faced

Capstone meta-skills:

• Pattern selection framework — force before name.
• Composition across projects — checkout, notify, pay, tenant.
• Communication — ADRs, design reviews, interviews.
• Subtraction — when and how to remove patterns.

Understanding the topic

Intent: Synthesize course into durable engineering practice.

• Selection — Foundations framework from early lessons.
• Composition — enterprise patterns at system seams.
• Communication — 5-part narrative + named RFCs.
• Subtraction — deletion sprints, when-not discipline.

Internal architecture

Capstone pattern map (all four projects):

Checkout:     Strategy, Saga, Circuit Breaker, Outbox, Adapter, Repository
Notifications: Strategy, Factory, Observer, Outbox
Payments:     Adapter, Strategy, Circuit Breaker, Saga (charge/refund)
Multi-tenant: TenantContext, Repository, Factory, Strategy (features)

Meta:         Selection framework, Refactoring to Patterns, When NOT, Deletion sprint

Visual explanation

Three diagrams map course arc, four capstones, and staff promotion signals:

Informative example

Promotion story template:

"Checkout rebuild (Q2): composed Saga + Breaker + Outbox at payment seam.
 Outcome: Black Friday 5× load, zero incidents.
 Removed: Abstract Factory for shipping — only 2 modes ever used.
 Removed: Observer sync to email service — replaced with Outbox.

 Payment LATAM (Q3): PaymentGatewayPort + SOAP Adapter.
 Outcome: new provider in 2 days vs 6 weeks.
 Removed: Singleton payment config — DI scoped config."

Execution workflow

Real-world use

Staff engineer promotion packets; architecture RFC templates; engineering blog posts naming patterns with outcomes; conference talks with production metrics.

Production case study

Staff promotion with removal stories:

• Three stories: checkout, payment, multi-tenant.
• Each included: 2 patterns removed per system.
• Outcome: promotion granted — judgment both directions.

Trade-offs

• Pro: course skills compound over career decades.
• Con: without practice, vocabulary fades — maintain habits.

Decision framework

• Force → pattern → compose → measure → remove if unused.
• Every system design: name patterns at seams.
• Every promo story: metric + removal.

Best practices

• Keep running "patterns I removed" list.
• Re-read selection framework before major refactors.
• Pair vocabulary with one production metric per story.

Anti-patterns to avoid

• Course complete → never think about patterns again.
• Only addition stories in promotion packet.
• Mechanical pattern application without force.

Common mistakes

• Treating capstone as finish line — it's starting line for practice.

Debugging tips

• When stuck on architecture: which force? which capstone is closest?

Optimization strategies

• Monthly 5-min cheat sheet review maintains vocabulary.

Common misconceptions

• Completing course ≠ senior engineer — practice compounds.
• Patterns include removal — not only application.

Advanced interview questions

Summary

You completed Design Patterns from force thinking through enterprise composition. Tell three capstone stories with removals — if you can do that, you own this course. Go build, name, measure, and delete.