ABOUT · HOW THIS IS WRITTEN
Who writes this, and on what basis
Some of this I work with daily. Some of it I wanted to learn properly, and writing it out is how that happened. Either way the page does not ask you to take my word for it: it names the documentation or specification it was checked against, and the date.
Like a mechanic who only trusts a repair after taking the part out, turning it over, and putting it back. Reading about it is not the same as having had it in your hands — and here, everything gets checked against the manual before anyone else sees it.
I write down what I learn as a developer, in a form someone without my context can follow. I work on domain-driven design in a large, long-lived enterprise system — money-handling logic, integration with systems I do not own, and modernising Java code older than my career. That is where the architecture writing comes from.
Explaining a thing well is the quickest way to find out whether you actually understand it, which is most of why this exists.
The site does not ask you to take my word for anything. Every page names the documentation, specification or source code it was checked against, and the date — the note at the foot of the idempotency piece is where an article says which. When a source turned out to contradict a page, the page changed. Four pages changed that way in August 2026.
Content is English first. There are no German articles yet. When they come, they will be written by hand for articles that have proven themselves rather than translated — a German article is allowed different examples and a different structure.
How a diagram gets made
01 — One picture, one sentence. The sentence is written down before anything is drawn. If it takes two sentences, it is two diagrams.
02 — The picture stands in the text. No frame, no widget box, no toolbar. It sits in the article, wider than the column, like part of the writing rather than an embed — the traversal walk-through is one page built that way.
03 — Colour-coded nouns. A noun in the prose wears the colour of its object in the picture, so you build the legend while reading without noticing.
04 — Motion only as meaning. Animation shows change over time or it does not exist. Nothing starts on its own, and reduced motion gets the end state.
Contact
Corrections and questions are welcome, and the address is on the Imprint page. If a page here is wrong, that is the fastest way to get it changed.
Colophon. Astro with a small number of islands. Diagrams are hand-written SVG with no framework, coloured only through tokens. No analytics that follow you elsewhere, no cookie banner, because there is nothing to consent to.
Newsreader — display. IBM Plex Sans — text. IBM Plex Mono — code.