Skip to main content

Book Exercise Lanes

This generated surface maps a learner-facing curriculum unit to its canonical source routes.

Curriculum surface​

  • Open learner-facing unit
  • Curriculum path: content/curriculum/foundations/semester-03-software-design/module-01-ood-foundations-and-smells/exercises.md
  • App: foundations
  • Semester: semester-03-software-design
  • Module: module-01-ood-foundations-and-smells
  • Unit kind: exercise
  • Curation level: generated_default

Learning objectives​

  • Turn Book Exercise Lanes into active practice instead of passive rereading.
  • Use the mapped source routes to supply examples, drills, or recovery help only when needed.
  • Finish the exercise with visible evidence that the skill moved from recognition toward recall or execution.

Prerequisites​

  • The earlier concept pages and practice tasks in the current module.

Source books​

  • clean-code
  • good-code-bad-code
  • head-first-design-patterns
  • ooad
  • refactoring

Source routes​

Clean Code​

  • /books/clean-code via Clean Code: Functions -- Do one thing, Clean Code: Functions — Do one thing, Clean Code: Meaningful Names -- introduction, Clean Code: Meaningful Names -- meaningful context, Clean Code: Meaningful Names -- pronounceable names, Clean Code: Meaningful Names — introduction, Clean Code: Meaningful Names — meaningful context, Clean Code: Meaningful Names — pronounceable names, Clean Code: Smells -- G12 Clutter to G18 Inappropriate, Clean Code: Smells -- G5 Duplication to G11 Inconsistency, Clean Code: Smells — G12 Clutter to G18 Inappropriate, Clean Code: Smells — G5 Duplication to G11 Inconsistency, Clean Code: Systems and Dependency Injection
  • /books/clean-code/chapter-03-functions-small-to-blocks-and-indenting via Clean Code: Functions -- Small, blocks and indenting, Clean Code: Functions — Small, blocks and indenting
  • /books/clean-code/chapter-10-classes-the-single-responsibility-principle-to-co via Clean Code: Single Responsibility Principle

Good Code Bad Code​

  • /books/good-code-bad-code via Good Code, Bad Code: Comments are a poor substitute for descriptive names, Good Code, Bad Code: Design with Dependency Injection in mind, Good Code, Bad Code: Use comments appropriately

Head First Design Patterns​

Ooad​

  • /books/ooad via OOAD: The Interface Segregation Principle, OOAD: Why Pixel is not SolidRectangle (LSP)

Refactoring​

  • /books/refactoring via Refactoring: Data Class and Comments, Refactoring: Data Clumps to Repeated Switches, Refactoring: Divergent Change to Feature Envy, Refactoring: Encapsulate Collection, Refactoring: Encapsulate Variable, Refactoring: Extract Class, Refactoring: Extract Function (Part 1), Refactoring: Extract Function (Part 2), Refactoring: Global Data to Mutable Data, Refactoring: Introduce Parameter Object, Refactoring: Long Function to Long Parameter List, Refactoring: Loops to Message Chains, Refactoring: Middle Man to Alternative Classes with Different Interfaces, Refactoring: Move Function (Part 1), Refactoring: Mysterious Name smell, Refactoring: Mysterious Name to Duplicated Code, Refactoring: Replace Conditional with Polymorphism (Part 1), Refactoring: Replace Conditional with Polymorphism (Part 2), Refactoring: Replace Primitive with Object

Supporting curriculum routes​

No supporting curriculum routes linked yet.

External enrichment​

No curated enrichment resources yet.

AI companion modes​

  • Explain simply
  • Socratic tutor
  • Quiz me
  • Challenge my understanding
  • Diagnose my confusion
  • Generate extra practice
  • Revision mode
  • Connect forward / backward

Source-of-truth note​

This teaching unit is learner-facing guidance assembled from multiple canonical book routes. Use the listed source books as the primary conceptual spine for Book Exercise Lanes, and treat outside material as supporting enrichment only.