Technical-Debt Ledger  Not Everything Gets Fixed
This generated surface maps a learner-facing curriculum unit to its canonical source routes.
Curriculum surface
- Open learner-facing unit
- Curriculum path:
content/curriculum/production/semester-10-capstone/module-02-implementation-testing/concepts/cluster-05-keeping-the-code-livable/15-technical-debt-ledger-not-everything-gets-fixed-supporting.md - App:
production - Semester:
semester-10-capstone - Module:
module-02-implementation-testing - Unit kind:
concept - Curation level:
module_curated
Learning objectives
- Explain Technical-Debt Ledger  Not Everything Gets Fixed as the disciplined conversion of design intent into working software with evidence, not just feature completion.
- Use Technical-Debt Ledger  Not Everything Gets Fixed to reason about feedback loops, test confidence, quality boundaries, and the cost of weak implementation discipline in a capstone project.
- Use
clean-code,good-code-bad-code,refactoring,software-engineering-at-googleto connect the learner page to code structure, verification strategy, and the practical mechanics of shipping a reliable implementation.
Prerequisites
- Comfort with the capstone domain, architecture direction, and the need to prove behavior through repeatable tests and evidence.
Source books
clean-codegood-code-bad-coderefactoringsoftware-engineering-at-google
Source routes
Clean Code
Good Code Bad Code
- /books/good-code-bad-code via
Good Code, Bad Code
Refactoring
- /books/refactoring via
Refactoring
Software Engineering At Google
- /books/software-engineering-at-google via
Software Engineering at Google
Supporting curriculum routes
- /architecture/semester-07-architecture-ddd/module-05-architecture-decision-records-reviews via
S7 M05 ADRs & Reviews - /foundations/semester-03-software-design/module-01-ood-foundations-and-smells via
S3 M01 OOD Foundations & Smells - /foundations/semester-03-software-design/module-05-applied-design-and-code-review via
S3 M05 Applied Design & Code Review
External enrichment
- Martin Fowler: Test Pyramid (
read_if_stuck) - Keeps testing strategy tied to confidence and feedback speed instead of accidental test sprawl. - Google Testing Blog (
optional_deep_dive) - Adds practical testing perspectives from large production systems that are useful when capstone quality starts to drift.
AI companion modes
- Explain simply
- Socratic tutor
- Challenge my understanding
- Diagnose my confusion
- Connect forward / backward
Source-of-truth note
This teaching unit is learner-facing guidance assembled from canonical book routes plus prior curriculum surfaces. Use the listed source books as the primary conceptual spine for Technical-Debt Ledger  Not Everything Gets Fixed, and use the supporting curriculum routes to reconnect earlier learner-facing explanations when needed.