To wrap up K2, you show the Kladde, explain places in your code and quiz yourself on what you built: on your own, or with someone around you who listens and asks follow-up questions. The wrap-up has the same three parts as in K1 (lesson 1.10.4), except that everything has grown: The Kladde is a web application with three kinds of visitors, it runs in Azure, and behind a single click there are now middleware, a page, the core, a store and a database.

Part What happens
Demo You show the running Kladde for 15 minutes: to a person who listens, or to a camera as a recording for yourself.
Code reading The person with you points at a place in your code and says: “Explain this place to me.” On your own, you let chance choose.
Practice questions Questions about the topics of K2, starting from your project, with answers to compare against.

As in K1, all three parts belong to learning; nobody grades them. Nobody expects you to know everything. What’s expected is that you understand your own code, give reasons for your decisions and can say how you’d find out something you don’t know yet. This lesson prepares all three parts; you spend most of the time practicing.

Where the Kladde stands

After lesson 2.11.12, the solutions have this:

  • All ten milestones are closed, every comment of the final review has an answer, and scripts/Test-Kladde.ps1 ends with the exit code 0.
  • The README leads a stranger from cloning to tearing down in Azure. docs/decisions.md names context, consequences and rejected paths for every decision.
  • Nothing is running in Azure right now: After milestone 10, you tore the Kladde down again.

If your files, classes or folders are named differently, keep your names and carry the steps over.