A working engineer, writing things down.
No personal brand, no growth funnel. Just the notes I wish I had found earlier.
What I do
I build and maintain backend systems: APIs, data pipelines, and the unglamorous glue that keeps a product running on a Tuesday. Most of my work happens at the boundary between “this is elegant” and “this can be operated by three people at 2 a.m.”
I have spent the last decade shipping software in teams of four to forty, across time zones and time-budget constraints. Along the way I developed a strong preference for boring technology, explicit trade-offs, and documentation that respects the person who reads it six months later.
I write in English for readers everywhere. The perspective is deliberately non-Silicon-Valley: fewer scale fantasies, more constraints, budgets, and the realities of maintaining what you built.
What this site is
A small, deliberate publication. Every essay starts from something concrete I worked on, measured, or got wrong. If a post has no first-hand artifact in it, it does not get published here.
It is also an experiment in ownership: no trackers, no cookie wall, no algorithmic feed. Full text through RSS, email if you want it, and a plain website that rewards reading rather than scrolling.
Editorial standards
- Every essay starts from a concrete artifact: a system I worked on, a measurement I took, or a mistake I made.
- Claims that depend on external behavior link to official documentation or primary research.
- Code samples are meant to be run; when a sample is illustrative rather than executable, the text says so.
- Substantive corrections are made in place and reflected in the essay's updated date.
- No sponsors, affiliate links, or paid placement. The arguments are mine.
What I write about
- Architecture — boundaries, migrations, and long-lived decisions.
- Performance — what readers actually experience, measured.
- Engineering — types, tests, and tools that pay rent.
- DevOps — pipelines and operations without heroics.
- Career — focus, feedback, and working across cultures.
- Writing — clarity as an engineering skill.
Elsewhere
The best way to reach me is email: hello@blog.waystoneai.online. I read everything and reply to most of it, eventually. Found an error? Say so; substantive corrections are noted in the essay. If you want new essays without an algorithm in the middle, use RSS or the letter.
Colophon. Set in Georgia and the system UI fonts, with a system monospace for code. Built with Astro, statically rendered, no client framework, no analytics by default. Hosted on a CDN. The source is plain Markdown in a git repository — the most durable CMS I know.