Capstone Review

The final session. We walk through everything built across all seven layers, confirm the full test suite passes end to end, and reflect on the complete journey from a single dictionary to a real, tested, documented application.

1. Learning Objective

2. Pre-Coding Quiz

Answer these before reading the concept explanation or writing any code. It is fine to get these wrong — that is the point. You need 4/5 to proceed to the lab.

3. The Concept — The Complete Country Explorer — End to End

The full architecture, traced from data to display

Every layer of this curriculum contributed one piece of a single, coherent pipeline. Tracing it end to end shows how deeply each layer depended on the one before it.

# The full pipeline, built up across all 40 sessions:

# 1. Layer 4 — a repository fetches and validates raw data
#    (from mock data, a JSON file, or a real API — interchangeably)
repo = CountryRepository(raw_data=fetch_countries_safely_and_adapt())

# 2. Layer 2 — raw dicts become real, validated Country instances
countries = repo.get_all()   # uses Country.from_dict() internally

# 3. Layer 2/3 — a CountryExplorer composes and manages the working collection
explorer = CountryExplorer(countries=countries)

# 4. Layer 3 — computed properties derive values safely, with no drift risk
print(explorer.total_population)   # @property, Session 26

# 5. Layer 6 — shared utilities used consistently across the whole app
results = explorer.search("ken")   # search.py, Session 38

# 6. Layer 2 — each instance formats itself for display
for c in results:
    print(c.summary())             # formatting.py, Session 37

Why the architecture held up under change

Country.summary() and grow_population() were written in Sessions 13-14. By Session 44, the project has been reorganized into a package, had shared logic extracted into utilities, and been pointed at three completely different data sources. Yet those original methods never needed to change — because they were built on clear, explicit contracts (Session 15) from the very beginning.

The final test suite, as proof

A test suite maintained honestly across dozens of structural changes — package reorganizations, new data sources, extracted utilities — is not just a checkbox. Running it one final time, and having it pass, is the closest thing to objective proof that this entire architecture genuinely works, together, as one coherent system.

The consistent teaching pattern, revisited

Sessions 12, 20, and 27 each paused to build a mental model — why classes exist, what state actually means, why mock data matters — before the following session introduced concrete implementation. This deliberate pattern is why the concepts in this curriculum should feel understood, not memorized.

4. Lab

What you will build

A final update to ARCHITECTURE.md, plus a verification pass across the whole project.

Step-by-step instructions

# pytest -v

# capstone_trace.py — a written trace of the full pipeline, in your own words
#
# 1. CountryRepository fetches raw data (mock / file / real API — Session 27-29, 42)
# 2. Repository validates and converts raw dicts into Country instances (Session 18, 30)
# 3. CountryExplorer composes the working collection (Session 16)
# 4. Computed properties (Session 26) and the shared search utility (Session 38)
#    operate on that collection safely
# 5. Country.summary() (Session 14, using formatting.py from Session 37) produces
#    the final, human-readable output

## Final Retrospective (Session 44)

**Most confident in:** The repository pattern (ADR-001) — proven across three
genuinely different data sources with zero changes to its own methods.

**Would reconsider:** [your own honest answer — e.g. the prop drilling
problem from ADR-003, or the size/granularity of formatting.py and search.py]

**Biggest lesson:** [your own honest answer, in your own words]

from country_explorer import CountryRepository

# reuse load_country_repository from Session 43
repo = load_country_repository("https://www.apicountries.com/countries")
results = repo.search("ken")
for c in results:
    print(c.summary())

5. Expected Files Changed

6. Commit Checkpoint

Once the lab is complete and you can explain every line, make this exact commit:

git add capstone_trace.py ARCHITECTURE.md docs/sessions/session-44/index.html
git commit -m "session-44: capstone review — full architecture trace, final retrospective, complete test verification"

7. Code Review Checklist

Go through your code line by line and check each item:

8. Post-Coding Quiz

Same 5 questions. Take it again now that you have written and run the code. You need 4/5 to mark this session complete.

9. Reflection Questions

Think through these after the post-quiz. No right answer — they are for discussion.

10. What Breaks If This Knowledge Is Missing?

11. What We Learned