Engineering reference at the level of mechanisms
Understand how it actually works.
Interactive explanations of how things work inside — for engineers for whom “how to use it” is not enough. Every claim is tied to a primary source: a PEP, a mailing-list message, a line of CPython, or a clause of a specification you can open yourself.
Flagship deep dives
Domains
5 LIVE · 4 IN PRODUCTIONAVAILABLE NOW
Python Deep Dive
How CPython actually runs your code. Every article is written against a pinned interpreter tag and says outright which behaviour is a language guarantee and which is an implementation detail.
AVAILABLE NOW
System Design
Architectural decisions that have an author, a date and a reason. Every pattern is read from the primary source — the text that first described it and the specification that says what it must do — never from retellings.
AVAILABLE NOW
Interview preparation
One mechanism, one lesson, ordered by how often it is asked: decorators, iterators and generators first. Each lesson explains the mechanism from the documentation and the CPython sources — measured, not remembered.
AVAILABLE NOW
Go
Go's scheduler, channels and garbage collector — read from the runtime sources and from the proposals where those decisions were made.
AVAILABLE NOW
SRE
Observability, error budgets and incident analysis — with numbers you can check, rather than slogans about culture.
Interview preparation
Not a list of questions with answers but a path. We did not guess the order — we collected sixteen public listings of interview questions and counted what turns up most. So it is an order by frequency, not a teaching sequence: for some lessons the prerequisite lies further down the line, and it says so next to the number — “come back after”. The lesson itself says none of this: it is about the mechanism, read from primary sources.
Python
From the code object to the memory model: decorators, iterators, context managers — mechanisms rather than memorised definitions.
SRE
Failures, observability, error budgets — what running things teaches, rather than what the vocabulary covers.
Go
The scheduler, channels, the garbage collector — one mechanism per lesson, as in every other track.
Free for registered readers while it is being tested. In exchange we ask for feedback: what was unclear and what was missing.
ENTER THE SECTION · 48 LESSONS →Every claim has a source
Articles cite PEPs, mailing-list threads and CPython pinned to a release tag. Where the documentation and the source disagree, we say so and show both.
Visualizations carry meaning
A hash table resizing, a generational collector pass, the GIL changing hands — step by step, each with a full text equivalent, so understanding never depends on watching an animation play.
Behaviour has a date
We do not write “Python does X”. We write: 3.11 changed X, 3.13 made it experimental, 3.14 made it supported but still optional.