Book Exercise Lanes

This module's exercise system is book-driven. Use the guide and practice pages first, then use these local chunks from Clean Code when you need more repetition or sharper review language.

How To Use This Page

1. Finish the matching concept page first.
2. Diagnose one real example before opening a chunk.
3. Prefer short refactors, review notes, and rewritten tests over passive rereading.
4. Keep a mistake log focused on what made the code expensive to change.

Lane 1: Readability and Intent

Use this lane when naming, comments, and formatting still feel subjective.

• Chapter 2: Introduction to Make Meaningful Distinctions
• Chapter 2: Interfaces and Implementations to Use Problem Domain Names
• Chapter 4: Comments Do Not Make Up for Bad Code to Explanation of Intent
• Chapter 5: The Purpose of Formatting to Vertical Density

Target outcomes:

• 10 renamed identifiers with justification
• 5 comment keep/remove decisions
• 1 readability audit on a real file

Lane 2: Function Honesty

Use this lane when functions look fine at first glance but become hard to trust on review.

• Chapter 3: Small! to Blocks and Indenting
• Chapter 3: Do One Thing to The Stepdown Rule
• Chapter 3: Have No Side Effects to The Error.java Dependency Magnet
• Chapter 7: Use Exceptions Rather Than Return Codes to Use Unchecked Exceptions

Target outcomes:

• 3 function refactors in small verified steps
• 3 side-effect diagnoses
• 2 error-handling cleanups that preserve intent

Lane 3: Tests and Safe Change

Use this lane when tests exist but do not yet make refactoring feel safe.

• Chapter 9: Keeping Tests Clean to Tests Enable the -ilities
• Chapter 9: Clean Tests to Domain-Specific Testing Language
• F.I.R.S.T. to Chapter 10: Classes
• First, Make It Work

Target outcomes:

• 3 rewritten tests that read more clearly than the originals
• 2 examples where tests made a refactor safer
• 1 short note explaining how a weak test suite blocks design improvement

Lane 4: Classes and Review Heuristics

Use this lane when the code works but feels bloated, sticky, or hard to review.

• Chapter 10: Class Organization to Classes Should Be Small!
• Chapter 10: The Single Responsibility Principle to Cohesion
• Chapter 11: How Would You Build a City? to Dependency Injection
• Chapter 17: C1 to G4
• Chapter 17: G5 to G11

Target outcomes:

• 2 class-responsibility reviews
• 1 small seam or boundary cleanup
• 1 review memo that names specific smells and change risk

Completion Checklist

• Completed at least two exercise lanes in full
• Logged at least 8 genuine mistakes and corrections
• Performed at least 4 real refactors or review passes
• Reattempted at least 2 weak examples after using the book chunks