The process
How these books are made
Every book is scoped, fact-checked, and signed off by a senior data engineer with 18 years of production experience — and every code example ships in a public repository where you can run and challenge it.
01
Scoped by the author
Each book's outline, case study, and audience level are defined up front from 18 years of building production data platforms, most of them in insurance and finance — the book covers the judgment calls that actually come up on the job.
02
Every claim is fact-checked
Every version-specific, behavioral, or numeric claim is verified against primary documentation — official docs, not blog posts — before a chapter can pass review.
03
Rewritten and signed off by the author
Every chapter is rewritten for judgment, voice, and production reality. Nothing ships without the author's sign-off.
04
Every example ships runnable
Every code example is run, broken, and published in a public repo where anyone can challenge it.
What this means for you
- Fresher than a print book on a 12–18 month cycle — this series ships on a monthly cadence.
- Verified — every technical claim traces to a primary source, not a blog post.
- Provable, not just claimed — every code example ships in a repo you can run yourself.