About

What this is

A personal site for long-form technical writing — mostly security research and incident analysis, across whichever domain the interesting failure happens to be in, plus the engineering around it. Entries are written to be read on their own and linked to each other, so the same idea can be referenced from several places rather than re-explained.

Nothing here is investment advice, and nothing here speaks for an employer. Post-mortems describe what happened and what the code got wrong; they are not disclosures, and they cover incidents that are already public.

The sections

Security

Incident post-mortems and vulnerability analysis — what broke, how the attack actually worked, and what the code got wrong.

Research

Longer-form investigation into how systems are designed, where trust actually sits, and the trade-offs that create risk.

Engineering

Building things — tooling, infrastructure, and notes from the workbench.

Notes

Short entries, tended rather than published. These get revised as understanding changes.

Maturity labels

Entries under Notes carry a maturity label, because publishing a half-formed thought is only useful if it's marked as one:

• Seed — rough and unfinished, captured to think about later. Expect gaps.
• Budding — taking shape, still being revised.
• Evergreen — settled, and revised only as understanding changes.

Entries in the other three sections don't carry a label; they're published when they're finished. All entries show an original publish date and, where it differs, a revision date.

Links between entries

Internal links are written as wiki-style references and resolved at build time — a link to a renamed or missing entry fails the build rather than shipping a 404. Each entry lists what links back to it, so a well-referenced note is discoverable from the things that cite it.