Topic-Specific Reading Assignment

Source and purpose

Use Good Code, Bad Code for contracts, testing boundaries, error handling, and maintainability. Find topic headings in your edition rather than assuming identical chapter numbering. Start with the module concepts and worked examples; reading should resolve an identified question.

Read, reconstruct, apply

Select the capstone's most important invariant and trace it from API input to persisted state. Add a failure-driven test at the boundary where it can break. Show which unit tests cannot establish the same property.

Before opening the source, write your prediction. After reading, close it and reconstruct the mechanism or argument. Then compare your prediction with the guided lab. Preserve a corrected misconception and one remaining question.

Completion and deeper reading

For the compact path, stop when you can explain the mechanism, pass the lab, and solve a changed scenario without the source. For the full-book degree, this task is a checkpoint within your scheduled complete reading, not a replacement for it.

Distinguish a book's conceptual model from a tool's current operational contract. Record the edition or documentation version actually used. Add another source only if it resolves a question that the primary source did not answer.