This is the first issue of what I am calling, with some private amusement, The Sculptor's Notebook. It is a small editorial project I have wanted to build for about three years and finally sat down to write.

I am Alex Chen. I have spent twelve years building distributed systems — first at a large e-commerce company you have used, then at two smaller infrastructure companies you almost certainly have not. The notebook is the place where I want to keep the writing I have been doing in private documents, slack threads, post-mortems, and the margins of textbooks. It collects them, edits them, and makes them legible.

What you will find here

The pieces fall roughly into four kinds.

Reliability and post-mortems. When something has broken and I have learned a generalizable lesson from it, I write it up here. I try to keep these to a single failure mode and a single fix, so they read in one sitting. The first one in this issue is about the day a retry helper became a load amplifier.

Small notes on languages. Type-system gotchas, runtime quirks, the kind of thing that ends up as a stored Slack message. Most of these are short. The intent is useful, not exhaustive. Most TypeScript posts on the internet do not need to be 2,000 words.

Sketches. A small tool, a small library, a small architectural diagram. The point is to show the whole thing in one piece of writing — the brief, the implementation, the trade-offs, and the things I would do differently next time. The Rust CLI in this issue is an example.

Field notes. Things I am reading, watching, or following from outside our own world — market analysis, AI release notes, the occasional academic paper. These are short and link-heavy. Treat them as a curated set, not a feed.

What you will not find here

I want to be explicit about a few things this is not, because I am tired of the alternatives.

It is not a course or a tutorial sequence. There is no curriculum, no funnel, no upsell. The closest thing to "next steps" you will see is a recommendation to read a specific book or a specific paper, and even that is rare.

It is not a thought-leadership platform. I do not have a take on the future of AI, the death of microservices, the rebirth of monoliths, or whether Rust will eat the world. I have opinions about specific things in specific contexts. When they generalize, I will try to say so. When they do not, I will try to keep my mouth shut.

It is not a marketing channel. Nothing here is intended to sell you software. The links to external sites are real things I read and recommend, not sponsorships.

How issues work

I am publishing in irregular issues, not as a continuous stream. Each issue collects three to six pieces, ships together, and gets a number. This is partly an editorial discipline (sit with a piece for a few days before publishing) and partly a respect for your time (you can read a whole issue in a sitting, or skip one entirely without feeling behind).

You can subscribe via email at the bottom of the homepage. Two issues a month, nothing else. If you would rather follow via RSS, the feed is /feed.xml — it always will be.

That is all. Welcome.