Deep Engineering
Search

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.

6 ARTICLES2 DOMAINSNO BEGINNER TIER

Domains

2 LIVE · 6 IN PRODUCTION

AVAILABLE 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.

4 SECTIONS5 ARTICLESENTER →

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.

1 SECTION1 ARTICLEENTER →
Go
COMING SOON
Databases
COMING SOON
Distributed Systems
COMING SOON
Linux
COMING SOON
Networking
COMING SOON
SRE
COMING SOON
NEW SECTIONIN DEVELOPMENT

Interview preparation

Not a list of questions with answers, but a path: the topics technical interviews are built around, with the same interactivity and the same knowledge checks as the articles. Order matters — each topic rests on the one before it.

  • Python

    From the code object to the memory model — what gets asked when the point is depth rather than memorised definitions.

  • SRE

    Failures, observability, error budgets, and the questions that come from running things rather than from knowing the vocabulary.

  • Go

    The scheduler, channels, the garbage collector — and how those mechanisms show up in interview problems.

Free for registered readers while it is being tested. In exchange we ask for feedback: what was unclear and what was missing.

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.