Level 6 · In practice

6.4Toolbox

Goal: have operational checklists and the essential Python commands.

Estimated time: 10 min · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

Delivery: 7 yeses — black + ruff, pytest, pinned requirements, hints + README, clean logs, slim Docker, CI + rollback.
Daily: venv, pytest, ruff, freeze and strict dev mode without fumbling.
Rule: one checklist ticked every time beats a method known by heart — under rush, you execute.

Nabil thread — the cards next to the expense tracker

After one year, both cards below stay next to Nabil's thread project: the delivery one displayed by the screen, the daily-commands one in his notebook. “What saved me, he says in substance, is not knowing the points, it is ticking them every time — especially on report Mondays.”

Adapt wording to your context, keep the structure: it is what avoids omissions and incidents.

Ready-to-use reference points

A good checklist makes delivery calm and omission-free; the right commands avoid fumbling. Adapt to your context.

Delivery (7 yeses)

black + ruff green, pytest green (nominal + limits).
pinned requirements, venv rebuilt as proof.
Hints at boundaries, README with install + usage.
Structured logs, clean errors, no bare except.
Slim Dockerfile + USER + .dockerignore (if container).
Green CI, secrets out of code, tagged version.
Rollback known and tested.

Daily commands

python -m venv .venv / activate / pip install -r requirements.txt.
pytest -q / ruff check . / black .
pip freeze > requirements.txt.
python -m pip list --outdated.
python -X dev script.py (strict development mode).

Common misinterpretation: “collecting checklists”. No. A checklist is only useful ticked and used: take the one for your next delivery, the others will wait.

Text version of the diagram (SEO / screen readers / translation): Two moments, two cards: 1) Delivery — 7 yeses (lint + tests, rebuilt venv, hints + README, logs, slim Docker, CI + version, rollback). 2) Daily — create/activate the venv, install, test, freeze, monitor in strict dev mode. Lesson: no more thinking under pressure, you run the card next to the thread project.

Ready-to-say script — validating a delivery (30 s)

“black + ruff green, pytest green? venv rebuilt from pinned requirements? README up to date, clean logs, slim Dockerfile? Green CI, secrets out of code, tagged version, tested rollback? If any no, we do not deliver.”

Copy-paste template — delivery tracking (1 line per point)

suivi = {
    "lint (black + ruff)": "OK / a reprendre",
    "tests (pytest nominal + limites)": "OK / a reprendre",
    "venv reconstruit (requirements fige)": "OK / a reprendre",
    "hints + README": "OK / a reprendre",
    "logs + pas de except nu": "OK / a reprendre",
    "docker slim + CI verte": "OK / a reprendre",
    "version + rollback": "OK / a reprendre",
}

VSE / small budget

One-page cards on the wall: the essentials (venv, tests, freeze) are enough.

SME Algiers

Plan local realities into the card: known contacts, Monday peaks, verified backups.

Remote / hybrid

Add a written-confirmation line to the tracking: at a distance, a dated validated delivery avoids misunderstandings.

Intercultural

Spell out labels in writing: what seems obvious (who validates, which venv) is not obvious to everyone.

Caution: General reminder: secrets, versions and rollbacks engage your organisation — secrets out of code, limited access and validation by the designated contact; this guide gives no legal advice.

48h challenge — apply tomorrow

Take 1 real project, run the “Delivery (7 yeses)” checklist and tick where it stands. Test the venv rebuild.

Section exit checklist

I ticked a checklist on a real project.
I can pull out delivery and daily commands at the right moment.
I did the 48h challenge or scheduled its date.

Self-assessment 1-5: tooling of my projects?dated use of checklists?

← Previous : Best practices & pitfalls (V3)Next : Field feedback (V3) →

Check your understanding

Nabil is about to deliver his automated report. What must he tick first?