Skill · Development · Get started with the developer's craft in Python: read, test, review, ship
Review someone else's Python code and get your own checked
Let the linter and the formatter (ruff check, ruff format) settle the mechanical part, understand the role of a small reviewable pull request, and review someone else's with a simple checklist: swallowed error, displayed secret, dangerous path, missing test, in actionable comments and with a verdict.
Start lesson 1The Development domain
- 1 lesson
- ~55 min of reading
- 1 quiz
- 0 proof lab
The path
Where it comes from, where it leads
What you need to know first, where you stand on this skill, and what it opens next. Your status is computed in your browser, from what you have read and passed.
Before · 1 prerequisite
Recommended before · 4
This skill, for you
Review someone else's Python code and get your own checked
Computing
It unlocks · nothing yet
No other skill requires it: it is an end-of-path skill.
The path through the foundations From the most upstream foundation to this skill: what is in place, what remains to read.
Lessons
How to learn it
1 lesson, about ~55 min, in program order. Each lesson ends with its quiz.
The program
1 lesson · ~55 min
Beyond the lessons
Assess, practise, pass the proof
Reading a lesson confirms nothing. A skill is confirmed by a passed quiz, practised in a guided lab, and put to the test by a challenge or a mission; an imported lab result is not verified by the site.
Assess yourself
1 quiz
At the end of the lessons: passed at 70%, it confirms the skill.
Proof
No proof
A practical proof is a challenge, a capstone or a declared lab.
Used by the mission “Ship an internal tool to other teams”, which has its proof.
Placement test
Preparing the questions…
Your answers in detail
For each question asked: your answer, the correct answer, its explanation and the page to reread.
Around it
Who requires it, who teaches it
Required by
Taught by
Same block · Get started with the developer's craft in Python: read, test, review, ship