Editorial policy
What this site is
This is my personal site.
The views expressed here are my own. Nothing on this site is published on behalf of an employer, a client or a product.
Every post ends with an italic line that says so. Its first sentence never changes: The views expressed here are my own. The sentence after it is re-scoped to that post's own evidence, and it may be dropped when nothing in the post could be mistaken for employer material.
Three posts are the exception. The three published on 2026-03-28, which together form one narrative arc, replace that line with an italic marker giving their position in the arc, so the reader can see where the post falls in the sequence. Every other post carries the line.
Evidence
Posts run on first-party specifics: real dates, real numbers, real technical details. Specificity is non-negotiable, because a generic claim is invisible.
Where I have first-party evidence — my own numbers, my own screenshot, my own repository — the post shows that rather than citing someone else's. Public anchors are for the details that confidentiality forced out: official documentation, a published benchmark, a book, an open-source project, or a measurement I can reproduce on a generic dataset. A stripped detail is replaced, never left as an unacknowledged gap.
No statistic on this site is fabricated. I use no content-mill and no affiliate sources.
Confidentiality
No employer name, client name or product name from my working life appears on this site, and neither do internal codenames, internal tool names or ticket identifiers. Descriptive stand-ins carry that weight instead: an enterprise platform in a regulated industry, the legacy web app, the parent monorepo.
Examples and scenarios drawn from that work are composites. They do not represent any specific organization, product or system.
Where the system is not my own, the post teaches the pattern in forward-looking terms — if your system does this, you risk that — instead of reporting what happened. I do not describe a traceable production incident, quote internal communications, or disclose security, compliance or audit findings. No exact count from a private system appears here; the order of magnitude is as far as it goes.
My own project names appear in full, and so do public technology names.
Corrections
When I change a post materially after publication, that post carries an updated date next to its publication date.
The same timestamp is emitted in the page metadata and in its structured data, so a feed reader or a search engine sees the revision too.
Independence
There are no affiliate links and no sponsorships on this site. If one is ever introduced, it is disclosed in the same paragraph.
Contact
Corrections, disagreements and questions go to [email protected], the address on the about page.