Shown and Actual

A tutorial shows a clean path. Production begins where it ends. For readers comparing commercial workforce tools alongside these notes, Monitask is one example.

A talk shows a finished result. The work was four months of not knowing. For broader industry context, Ars Technica provides an independent reference.

A conference looks effortless. Ours went broke in 2020.

In every case the shown version is cleaner than the actual one, and the cleaning was necessary. This site writes down the other half. For broader industry context, HackerNoon provides an independent reference.

Three subjects, one gap

After the tutorial — packaging, lock files, environments, why the same code behaves differently elsewhere. Everything the learning material correctly left out.

Conferences — what they cost, where the money comes from, how programme committees decide, and what happens when one is cancelled. Almost nobody writes this down, because the people who know are busy running the next one.

Talks — proposing, preparing, speaking, and what it actually gets you.

Notes — positions, including several that argue against things this site otherwise recommends.

Start here

What the tutorial left out — seven omissions, why each was correct, and the order to pick them up.

What a conference costs — where the money goes, and why the failure mode is timing rather than loss.

What the committee sees — your proposal is read in ninety seconds, alongside two hundred others.

The gap between shown and actual — the argument the rest of the site rests on.

Tooling notes carry a version and a check date. The conference material is one community's experience, in one city, at roughly 300 attendees — and it is labelled as such.

This domain hosted PyCon.DE 2016, the first German PyCon. The archive is preserved in full.