Skip to content

Reference

Reference Position

flowchart TD
  family["Python Programming"] --> program["Python Functional Programming"]
  program --> reference["Reference"]
  reference --> review["Design or review decision"]
  review --> capstone["Capstone proof surface"]
flowchart TD
  trigger["Hit a naming, boundary, or trade-off question"] --> lookup["Use this page as a glossary, map, rubric, or atlas"]
  lookup --> compare["Compare the current code or workflow against the boundary"]
  compare --> decision["Turn the comparison into a keep, change, or reject call"]

Read the first diagram as a lookup map: this page is part of the review shelf, not a first-read narrative. Read the second diagram as the reference rhythm: arrive with a concrete ambiguity, compare the current work against the boundary on the page, then turn that comparison into a decision.

Use this section when you need durable language, review criteria, or proof prompts rather than a reading route. Keep these pages open while designing or reviewing code in the course or the capstone.

Pages in this section

  • Glossary for the course vocabulary that appears across modules and the capstone
  • FP Standards for the stable engineering rules that define acceptable functional design in this course
  • Functional Anti-Pattern Atlas for recurring failure shapes and the repair route back to the course
  • Boundary Review Prompts for sharper keep, change, or reject questions during review
  • Review Checklist for code review and capstone inspection
  • Self-Review Prompts for turning module ideas into retrieval practice and design judgment
  • Topic Boundaries for deciding whether a question belongs in the course center, on its edge, or outside it