The final project
Scope, automated checks, human review and what belongs in the README.
10 min read
The final project is the principal piece of evidence in your record.
Scope. A narrow application that is complete, handles its failure cases and is documented is assessed more favourably than a broader one left unfinished. Choose the scope on that basis, then spend the remaining time on the parts that are usually omitted.
Automated checks. The repository must be reachable, contain a README, and show a commit history consistent with how the work was produced. A single commit containing a complete application is referred to human review.
Human review. Whether the README allows someone unfamiliar with the project to run it; whether commit messages describe the changes; whether failure paths were considered; whether the application does what the README states.
README. What the project is, the problem it addresses, how to run it locally, and what is deliberately out of scope. The final section is expected rather than optional.
Demonstration. A deployed URL or a short recording. Not mandatory, but it removes any question of whether the project runs.
Go deeper
Lessons are not assessed. Progress towards the certificate is recorded from the work you submit. See all requirements