The final project is the last section of K2. Hardly any new tool comes in. Instead you bring together everything you learned in modules 2.1 to 2.10 and turn many separate parts into an application that a small IT office could really use. At the end you show the Kladde in a demo, explain places in your code and answer practice questions.

This lesson is the planning for it. You compare what the Kladde can do with what it should be able to do, write the missing parts as issues and split them so that every pull request stays small enough for a thorough review.

How the final project works

The module has 60 hours in 13 lessons. Ten of them are milestones: each one finishes a piece of the Kladde, with tests for every acceptance criterion and a review for every pull request.

Lesson Content Hours
2.11.1 Planning 3
2.11.2 Milestone 1: Contacts and companies 5
2.11.3 Milestone 2: Appointments in the office 5
2.11.4 Milestone 3: Free times and booking 5
2.11.5 Milestone 4: Confirmation and outbox 5
2.11.6 Milestone 5: Importing tenders 5
2.11.7 Milestone 6: Searching tenders 4
2.11.8 Milestone 7: Two languages 4
2.11.9 Milestone 8: Accessibility and security 5
2.11.10 Milestone 9: Completing the tests 4
2.11.11 Milestone 10: Delivering to Azure 5
2.11.12 Review and polish 5
2.11.13 Wrapping up: demo, code reading, practice questions 5

This module has no task to hand in. Progress shows as you go: every milestone is only done when its tests are green (judged by the exit code) and a second person has read each of its pull requests; lesson 2.11.12 says who that can be. At the end come a final review of the whole Kladde (2.11.12) and the wrap-up with a 15-minute demo, a code reading and practice questions (2.11.13), which nobody grades.

The milestone lessons are built differently from the ones so far. Each begins with the issue from this planning, shows how to split the milestone, explains the parts that are new, and for everything else points to the lesson where you learned it. You build most of the time yourself.