08 — Journal
Writing from the build
Notes from the work: how systems are designed here, what breaks in production, and the reasoning we would want to read six months later.
- Posts
- 6
- Categories
- 5
- Cadence
- Weekly
- Format
- Long-form
All writing
- AI & Machine Learning2026-08-14 · 12 min
Write the evaluation before you write the model
Leakage, sampling and the small set of habits that stop a model from looking better than it is.
- Security2026-07-30 · 10 min
Threat modelling for services that are still small
A one-afternoon method for mapping assets, trust boundaries and mitigations before a service gets large enough to hurt.
- Engineering2026-07-16 · 8 min
Getting oriented in a codebase you did not write
A repeatable route from clone to confident change, without reading every file.
- Career2026-07-01 · 7 min
Writing an engineering portfolio that reads well
What reviewers actually read in a project write-up, in what order, and what they skip entirely.
- Engineering2026-06-18 · 11 min
Infrastructure you can reason about at 3am
Reproducible environments, boring deploys and the observability minimum that makes incidents short.
Questions
Questions, answered
01Who writes the journal?
The platform team and reviewing engineers. Every post comes out of work that actually shipped, not from a content calendar.
02How often is it published?
Weekly on average. A post goes out when the reasoning is worth reading, not to fill a slot.
03Can I republish a post?
Quote freely with attribution and a link back. Ask the contact desk before republishing in full.
04Can members contribute?
Yes. Write up a build or an incident, send it through the contact composer, and the editorial desk will review it.