Week 9: Clean Code (QA)
Goal
This week’s goal is to learn by doing, practice clean code, design, and refactoring patterns on real code while internalizing the concepts and your team’s own coding commitments.
Expected Results Before This Week
Weekly Progress Check rules
- Be prepared to show your results at the beginning of class.
- Presenting teams are selected randomly each week. The same team may be selected repeatedly.
- If your team is selected and there is no relevant work recorded before the session, 3 points will be deducted. Any relevant demonstrable work avoids the deduction: the weekly score is then between 0 and +3 points, depending on quality and completeness.
- A missing expected result can cause a point deduction only once, but you should still catch up: later work may depend on it, and these results usually contribute to the tasks required for your desired grade. More about salary for tasks
How Weekly Progress Checks work · More about penalty and bonus points
This week's expected results
- Your team’s repository already contains working source code with identifiable modules or features.
- You can point out which parts of the system are at least structurally implemented, even if not yet polished or complete.
| Title | Duration |
|---|---|
| TBA | |
| TBA | |
| TBA | |
| When and How to Refactor | 30 minutes |
| TBA |
Notes for tutors:
1: TBA ()
Section section\basic\code_for_humans.md not found.
2: TBA ()
Section section\basic\my_zen_of_python.md not found.
3: TBA ()
Section section\basic\the_feeling_i_leave_in_code.md not found.
4: When and How to Refactor (30 minutes)
Why is this useful for me?
Things you learn and experience in this session will help you to solve the following tasks:
Background
Activities
5: TBA ()
Section section\advanced\clean_code_advanced.md not found.