Skip to main content

Reference and Selective Reading

This capstone module has no new primary book. The reference page exists to help you find the right prior-semester material or the single external page when the concept page is not enough. Nothing here is required reading.

Source Roles​

SourceRoleWhy it is here
Concept pages (this module)Primary teaching sourceThe main teacher for all 15 concepts
Prior semester modulesDirect prerequisitesReactivate habits; do not re-read
The Pragmatic ProgrammerSelective reinforcementRevisit chapters when judgment is fuzzy
External URLs belowTargeted escalationOne or two per cluster, curation-verified

Read Only If Stuck​

Walking Skeleton and Vertical Slices​

Test Pyramid for a Real System​

Quality Gates and Feedback​

Defect Reduction Under Pressure​

Keeping the Code Livable​

Optional Deep Dive​

Cross-Semester Map​

Concept in this modulePrior-semester source
01 Walking skeletonS10 M01 Domain Analysis & Architecture Design
02 Vertical slicesS3 M05 Reviewable Commits and PR Shape
03 Steel threadS10 M01 integration-point inventory
04 Unit testsPrior testing track; S3 M02 Refactoring
05 Integration testsS6 M04 Transactions & Consistency
06 End-to-end testsS10 M04 Operational Readiness (smoke tests)
07 Pre-commit hygieneS3 M05 Automated Checks as Part of Design Hygiene
08 Coverage floorS3 M02 Refactoring (safety nets)
09 Contract testsS6 M04 Transactions & Consistency (shape drift)
10 Bug triageS10 M04 incident severity
11 Regression-firstPrior testing track + S3 M05 review practices
12 Flaky test diagnosisS4 systems programming (race conditions)
13 Refactoring cadenceS3 M02 Refactoring; S3 M05 stewardship
14 24-hour self-reviewS3 M05 Review Rubrics
15 Debt ledgerS3 M05 Pragmatic Tradeoffs cluster

External Source Map (validated)​

URLRole for this moduleValidated
https://martinfowler.com/bliki/TestPyramid.htmlOriginal test-pyramid shapeYes
https://martinfowler.com/articles/practical-test-pyramid.htmlFull modern practical treatmentYes
https://dannorth.net/introducing-bdd/Behavior language and test namingYes (redirected to blog path)
https://docs.pact.io/Consumer-driven contract testingYes
https://refactoring.com/catalog/Named refactors for deep-refactor windowsYes
https://google.github.io/eng-practices/review/reviewer/standard.htmlIndustry code-review standardYes
https://martinfowler.com/bliki/TechnicalDebt.htmlTech-debt metaphor (Cunningham + Fowler)Yes
https://www.mattblodgett.com/2020/09/start-with-walking-skeleton.htmlPractitioner definition of walking skeletonYes
https://medium.com/@QuarkAndCode/how-to-fix-flaky-tests-reproduce-diagnose-prevent-in-ci-cd-60f45226851fFlaky-test practitioner checklistYes
https://arxiv.org/html/2511.14002v1FlakyGuard / industrial flakiness validationYes

Concept-to-Source Map​

Primary conceptBest source if stuckWhy
Walking skeleton: thinnest end-to-end sliceMatt Blodgett: Start With a Walking SkeletonCleanest practitioner restatement
Vertical slices over horizontal layersMartin Fowler: The Practical Test PyramidImplies vertical slicing by how each level is exercised
Steel threadS10 M01 integration-point inventoryThe thread is chosen from your own architecture
Unit tests: where they add leverageMartin Fowler: Test PyramidWhy the base is broad
Integration tests: boundaries and fakesMartin Fowler: The Practical Test PyramidFull taxonomy incl. service vs contract
End-to-end tests: the expensive fewMartin Fowler: Test PyramidWarnings against top-heavy suites
Pre-commit hygieneGoogle eng-practices: Standard of Code ReviewWhy automation frees reviewers for design work
Coverage as a floorMartin Fowler: The Practical Test PyramidDiscussion of coverage limits
Contract testsPact: IntroductionCanonical consumer-driven model
Bug triageS10 M04 incident severitySame severity scale, operational context
Regression-first fixingDan North: Introducing BDDTest-naming that reads like the failure mode
Flaky test diagnosisHow to Fix Flaky TestsMatches the five-cause model
Refactoring cadenceRefactoring: CatalogNames for the moves you plan
24-hour self-reviewGoogle eng-practices: Standard of Code ReviewThe rubric you apply to yourself
Technical-debt ledgerMartin Fowler: Technical DebtThe interest/principal framing