This is mostly a very messy conglomeration of two template files and a bunch of JavaScript and CSS applied to the same underlying build script and content taxonomy that I've been very happy with for quite a while. There was a very oblique reason for this change, which was my friend Ryan asking for a blogroll of folks whose writing I enjoyed. I couldn't figure out a nice way to surface this, even though I did have it in my site's repository already.

So one thing led to another, and here we are. This is certainly not the greatest implementation of this kind of idea that has ever existed, but the thing that I like about mine compared to many of the others that I've seen is that I get to take advantage of what is approaching a decades-long corpus of writing and thinking — much of it sloppy, but all of it mine.

I hope you enjoy it too, and please let me know what feels janky or outright buggy.

I don't want this to be a particularly harsh or negative essay, so let me start with how I made the decision — which was, in retrospect and given how Buttondown has grown, laughably naive. I chose Django and Vue because I had just started a job in which I would be writing Django and Vue, and I didn't want to have to context switch. I was a pretty mature Django developer at that point but an immature Vue developer, so I thought of this as a great opportunity to learn the framework.2In a fit of cosmic irony, said company has since gone under. Buttondown persists.

To be clear: on the scale of poor technical choices I've made with Buttondown, Vue is certainly not in the top three. It might not even be in the top ten.

What I do find myself ruing about Vue falls into two buckets: minor aesthetic differences, and what I would describe as a permanently lagging ecosystem.

In the realm of minor aesthetic differences, I've found the core SFC abstraction painfully limiting. It introduces weight — a tax, really — on component refactors and small bits of shared code.

Vue's clumsy migration from 2 to 3, and its inability to rip the Band-Aid off and get everyone onto the <script setup> style, has also fragmented the documentation and the general zeitgeist. I think this compounds what was already a problem even back then: the sheer enormity of React's user base makes its ecosystem that much better.3I don't think it's a coincidence that Evan's most successful projects — Vite and, more recently, VoidZero — have been the ones that target the entire JavaScript ecosystem rather than just Vue.

We've had to reinvent things that would be trivial dependencies to pull in over in React land, like sprites and Storybook. We've had to completely shift our use of libraries that originally targeted both React and Vue, because they eventually abandoned Vue (Headless UI being the most painful example).

None of this is dramatic or exponentially painful. Buttondown as a business would probably be somewhere between 5—15% larger if we were using React instead of Vue — which is non-trivial, but not worth rewriting the entire author-facing application over.

Go, you Huskies!

It's not a lie... it's a gift for fiction.

For all of his foibles, Mamet can write dialogue like no one else, and the chance to hear his words in the trappings of a sort of proto-Hail, Caesar! — a film about filmmaking — is too good an opportunity to pass up.

This movie is cynical and odd. It contains a bunch of great writing, delivered by horrible people, portrayed by actors you are excited to see; the net effect is a film that you feel slightly more rotten for having seen.

And yet: the best deconstructions are also love letters. Mamet names the mayor of this town — which could essentially be Bedford Falls — George Bailey. He also quickly dispenses with the traditional narrative (a large capitalist entity rolling over and squashing small-town people with big hearts) by laboring to show us how strange and urbane and awful the townspeople are, too.

Almost everyone is terrific in this, in all senses of the word, and in ways that feel just self-referential enough to suggest recursion. Alec Baldwin's main plot arc is his inability to not sleep with underage girls; the girl in question (Julia Stiles) is written as a pursuer rather than a victim. Rebecca Pidgeon steals the show as a sort of saintly manic pixie dream girl who also incites much of the plot by leaving her fiancé on a whim.

It is also — lest any of this obscure the point — an intensely frenetic and funny movie.

Consider the ledger:

• The character work is borderline incomprehensible — though I love Rick Masters altogether, and I love that his arc is left largely unresolved.
• The direction is beautiful (Friedkin! Müller!) and hamstrung by an atonal, often sitcom-esque pacing.
• The chase scene's heights are cancelled out by some truly awful reaction shots from John Pankow.

And then there's the sense that the whole thing somehow exists as a fever dream, untouchable by the artifice of any character besides our central few.

The ending wants you to interpret it either very somberly or very trivially, which is not unlike the rest of the film. Perhaps I needed to grow up a decade earlier to appreciate it.

So one version of this review is an impossible hypothetical: if it had been finished, I think it probably would have been a greater work than Infinite Jest. Which — again, I stress — is one of my favorite books of all time.

But it wasn't and it's not. So what is it? It's impossible to really talk about the themes or the choices made in this book unless you want to do so as theorycrafting. Many of its deeper meanings are left mostly submerged: available for examination, but not for excavation.

Instead, I think a reader should consider The Pale King as if it were a collection of short stories, all set in the same place, and see how it sits with them then. In that light. it's bizarre and atonal and sloppy and really, really terrific.

One historical way to build power has been creating leverage through engineering: an engineering organization that can generate value quickly or cheaply is better than one that can't.

Gauging the efficacy of an engineering organization is, sadly, an unsolved problem, but three useful aspects are:

1. speed
2. stability
3. cost

These must be considered as vectors, not points; any codebase's snapshot of any of these is much less important than the organization's ability to change it in line with overall goals.

I find myself constantly amazed at the efficacy of LLMs while also being surprised at how and why they fail a given task in uninteresting and inscrutable ways.

Models from frontier labs are currently very cheap (but could soon not be); they are very fast (but tend to lower their own velocity over time); they are good at improving some but not all aspects of stability.

Just as Warhol said that a Coke is a Coke and you're drinking the same bottle as the president, there is little variance across model performance for consumers. The marginal advantage of various point-level improvements quickly accretes to the commons thanks to open-source.

To the extent that you cede responsibility for your codebase to an LLM, you diminish your ability to generate leverage from your codebase over a sufficiently long-term horizon; phrased differently, ceding responsibility to the LLM means sacrificing wisdom. Is that a big deal? Well:

1. My experience with LLMs is such that, at least today, I can be wiser about a codebase than an LLM. (Reasonable people can disagree!)
2. My experience with running a business is such that, at least today, wisdom is a useful lever to build a codebase which provides competitive advantage over incumbents. (Reasonable people can disagree!)

Discussions about our current rituals (hand-writing code, reviewing pull requests, etc.) are really discussions about the value of engineering as a process vs. the value of engineering as something which produces an artifact.

It is a reasonable position for someone to think that the value of engineering as a process is going to zero. But if you believe that, you better have a coherent answer of where your competitive advantage is coming from once every other organization you compete with is using the same tools as you.

This is not a novel desire. Linear offers it out of the box via Linear Asks — on the enterprise plan. I am a cheapskate, and I could not justify a couple hundred extra dollars a month for this one thing. So I set out to jerry-rig it myself.

The answer is honestly kind of funny, and kind of sad. Behold:

And it works!

Ideally this is the sort of thing Slack's workflow builder does natively, and my bar was low: I needed neither polish nor perfection but simple mechanical routing. The blocker is in identity mapping, as far as I can tell: the Slack–Linear integration has no canonical way to map a given Slack user to a given Linear user, and I want every reported issue assigned to the person who reported it.

(That requirement is probably a liability at a larger company. If you have forty engineers and a real code-ownership graph, "assign it to whoever complained" is exactly the wrong default; you want triage, routing, et cetera. We are thankfully, blissfully unaware of such problems thus far. The person who notices the paper cut is, nine times out of ten, the person who should fix it.)

So: duct tape.

Art has to offer something other than stylized despair.

Something I hadn't really considered before reading 10:04: my experience with autofiction has been almost entirely dominated by women writers (Cusk, Offill, Lockwood, Nelson). There is probably something interesting to examine here — a continuation of A Room of One's Own, Woolf extended onto the present, a sort of rebellion by the feminine to allow (and demand) their inclusion in what is allowed to be fictionalized, which is to say what is allowed to be fiction.

There's also probably something to be said about the inherent power dynamics of autofiction, and 10:04 spends time discussing this at length in a way characteristic of the rest of the book: circuitously, coyly, and in a manner I would otherwise find annoying if the author were not such a strong stylist and clever thinker:

that part of what I loved about poetry was how the distinction between fiction and nonfiction didn't obtain, how the correspondence between text and world was less important than the intensities of the poem itself, what possibilities of feeling were opened up in the present tense of reading

She said she hoped she would see me again, and the next thing I knew I was running through light snow back to my dorm, laughing aloud from an excess of joy like the schoolboy that I was. I had overwhelming sense of the world's possibility and plentitude; the massive, luminous spheres burned above me without irony; the streetlights were haloed and I could make out the bright, crustal highlands of the moon, the far-sprinkled systems; I was going to read everything and invent a new prosody and successfully court the radiant progeny of the vanguard doyens if it killed me; my mind and body were as a fading coal awakened to transitory brightness by her breath when she'd brushed her lips against me; the earth was beautiful beyond all change.

Nothing in the world, I thought to myself, is as old as what was futuristic in the past.

And this is ultimately where my analysis of 10:04 starts and ends. Ben Lerner is, at least in this estimation, a smart and clever prose stylist whose powers of observation and reflection are interesting but not meaningful.

I enjoyed this book, and I could get ensorcelled — however briefly — in the trappings of its recursions. But whatever heights it reaches, the book is trapped by the fences of its context. I don't mean this as a slight against anyone but myself; I simply don't think I have that much to learn about the world from learning about Ben Lerner.

And despite all the lampshading, this is a book by Ben Lerner about Ben Lerner. Reading it has made me more interested in seeing his other work — and less interested in ever recommending this one to someone else.

Flirting with Disaster works very, very well when you examine it through its screwball sensibility. Russell strikes a fascinating balance with this script: almost every single line read is delivered in a mostly naturalistic way. Nobody is playing a cartoon character. These are real, genuine — albeit silly and ridiculous — adults.

But the off-screen action, the camera movement, and the editing almost serve to undermine them. Take Richard Jenkins, absolutely playing his pants off, getting passed between two cars in a long-running bit about him being the fifth wheel.

Which is not to say that the naturalism makes the film unfunny. I laughed more than I was expecting to — but the laughs often came from a place of realism, like Mel's parents going back and forth about the car, or just about any scene with Mary Tyler Moore.

Part of the real joy of watching it was not knowing whether a line would be played straight or for laughs, even though both ended up serving the same end. The movie never has much in the way of serious tension or suspense, but the final act — Mel's parents showing up to save (or sabotage) the day, the smash cut, and the immediate turnaround — single-handedly raised my estimation of not just the script but the film as a whole.

So: a great script, a wonderful plot, and a then-modern take on screwball comedy, a genre for which I have a very soft spot. And it's filled with extremely great performances from actors I love — I haven't even mentioned Alan Alda and Lily Tomlin, playing husband and wife. As if things could get any better!

So why haven't I decided that I actually like it?

I think it ultimately comes down to the fact that Ben Stiller's character fucking sucks. I know this is not an interesting or trenchant critique. One interesting dynamic of older films is that we tend to otherize their characters, viewing them through a different lens than we would a contemporary protagonist — even decades later.

But Mel is the father of a literal four-month-old whom he spends maybe five seconds of the film holding or addressing, and he is mostly disinterested in his wife compared to the wiles of Téa Leoni.

For every note that lampshades the fact that yes, we know this guy is a scumbag, there's another that attempts to slightly humanize or redeem him. And so where I had difficulty — right up until the final act — was not being sure how seriously I should take this film and its foibles.

Screwball comedies tend to involve at least one relatively well-meaning character. By the end of this one, the closest thing we have to heroes are Mel's parents: played initially for one-dimensional laughs, they end up saving the day, acting only in service of protecting and rescuing their son.

(This all got a little more serious than intended.)

This is a good, funny film. There are moments of broad screwball comedy, and there's also some great, dry wit. You get to see two actors I tend to think of in a much older mode — Josh Brolin and Patricia Arquette — playing young, attractive, exciting people.

You won't have a bad time with this movie. Just don't spend any time at all caring about these people, because it might distract you from the jokes.

The logic for this inevitability is simple. Interviews derive the vast majority of their value from their audience, and the single biggest influence on that audience is the subject of the interview. Interviewers are therefore incentivized to land subjects who are as popular as possible, and one way of doing so is to make the value proposition for those subjects as positive as possible — which generally means letting the subject completely drive the interview and use it to their own ends. Both parties get to leverage the audience and reach of their counterparty; it's a win-win relationship for everyone except the listener. 1I've been grumbling about this for a while: my The best podcasts list from 2017 is a receipt.

There is one small exception to this rule that I've noticed: a single podcast called Talk Easy, hosted by Sam Fragoso. Sam tends to interview people in the entertainment spheres — movies, television, and writing in particular.

His interviews are remarkable in three ways:

1. Bless his heart, he has the voice of a caricature of an NPR interviewer.
2. His depth of research for every interview is startling. He'll dig up — and quote at length — excerpts from a writer's first gig at their college paper, or from a blog they wrote under a pseudonym.
3. He asks legitimately meaningful questions, and successfully elicits responses from his subjects that are unique and candid — a feat I have not seen replicated by any other interviewer who regularly talks to people of the same repute.

How does he do it?

Perhaps this is naive of me, but I think it's because he so clearly approaches every conversation with genuine candor and empathy. He builds a surprisingly intimate rapport with his subjects in a very short amount of time, which lends him the credence to ask them harder questions. Those harder questions are often telegraphed, but never inorganic or mean-spirited. He gets his subjects to discuss painful things — or their own hypocrisies — in a way that I find genuinely rewarding, unlike most other podcasts in this format.

Unlike every other podcast in this format, actually. The antidote to pablum, it turns out, is not hostility; it's homework and a little bit of tenderness.

Whether intentional or otherwise, a lot of airtime was given in the brief pre-release hypecycle to Astra's ability to generate things that looked cool. Lots of games, renders, and canvas examples cluttered my various timelines.

This makes sense: 3D stuff is cool; most people don't really have a sense of the toolchain involved in things like this, and how much of the effort is on the part of the LLM versus the structures it builds upon is somewhat obfuscated; platforms like xtheeverythingapp.com tend to reward videos and animations.

I try (unsuccessfully) to remain sober about all of this. But the release of the model, coupled with things like the deeper information around the Hugging Face incident and Collusion.wiki, did ignite a bit of a spark in the back of my head — thinking, as always, however briefly, about the chance that things are really different this time. Did we solve software?

Then I started using the model.

And much like my quasi-review of Fable 5.1, I found that the model is good! It's hard for me to really compare and contrast it against Fable 5.1 because I didn't do formal comparisons or anything like that; I just tried throwing a couple of problems I was working on against it, and it handled them all well and the things it couldn't handle were generally due to lack of context and agency, not lack of horsepower.

It's very smart and capable, but limited by the tools and harnesses and contexts it has access to (words I deploy in the broader sense, not the industry-specific ones.). All of this mirrors almost exactly my sense of wonder followed by disillusion when I started really kicking around Fable for the first time. 1Though I do maintain that Fable pre-DOD was a slightly different beast, and felt more akin to a real change in how I programmed.

Astra is very good at a lot of things; for me, though, it is increasingly extremely competent at tasks that have already been solved by faster, cheaper models. And at least personally, as someone who runs a non-trivial business where the risk of false positives vastly outweighs the attractiveness of sheer velocity, I struggle to find the right balance here between exploring the boundaries of what is possible and remembering that right now my job is no longer that of a technologist but of an industrial designer.

I run a small business where we have absolute license to use models at will, so long as we do so judiciously and securely. I talk about them for no economic or personal reason 2Disclaimer: I am, as of this writing, an investor in Anthropic through an acquisition they made.; I want to understand (and thereby master) them out of a conviction that they'll improve my business.

I bring that up because I found myself vigorously nodding along to this essay from Armin Ronacher, who writes (amongst other things, which I agree with):

I'm more and more convinced that all of AI engineering is Neijuan (内卷, meaning curl inwards). In China it describes a system that demands ever more effort and competition without improving output. The way in which it sometimes shows up in the West is the 996 nonsense. The English term for Neijuan is "Involution" from the book Agricultural Involution. Agricultural involution describes the intensification of farming that raises productivity per square meter while leaving productivity per head unchanged.

One way of thinking about LLMs (or any technology) is dichotomous:

1. There is the raw power a given model can generate,
2. and then there's the design and manufacturing of interfaces that can use that model in useful ways.

The biggest step function in software engineering over the past few years was not a specific model but Claude Code. Astra and Fable have improved my life less than full support for subagents and worktrees did.

I get that it's unfair of me to pretend those two things are discrete! I don't have enough intelligence to understand how raw power acts as a proxy for various other implications outside my industry. But I do — at least for now — have enough experience to understand that right now it's a poor proxy for operational leverage in mine.

For the past sixty days, Buttondown 1I take liberties here and throughout the essay: this was all Matias' doing. He also wrote a great piece on our migration to Planetscale, and also cites Planetscale's recommendation for this experiment. ran a scheduled LLM invocation once a day. Every morning it would look at the previous few days of database load in PlanetScale, and — if, and only if, it was sufficiently confident — it would open a pull request containing exactly one performance improvement to the seam between our app and our database.

I think of this as a longitudinal study, and a fairly cheap one: LLMs are extremely well suited to performance optimizations, precisely because such optimizations can be evaluated and then trivially discarded. 2We used GPT 5.3 Codex High for this, but I suspect our outcomes would have been broadly similar with whatever model we reached for.

Two months down, and here's where we're at:

1. We decreased our overall database reads by 25% for no cost or effort beyond that of reviewing the PRs.
2. We are stopping the experiment.

Let me frame the rest of the post with the most important takeaway for a prospective reader: this was an undoubtedly positive-value experiment, and I recommend everyone try it if they're able. Even setting the epistemology aside, the performance benefits we banked were unambiguously worth the small amount of time I'd spend reviewing PRs every morning. The only reason I'm not dwelling on the upside is that I think the flaws are more instructive than the wins.

So, with that out of the way —

Firing our DBA

25% improvement! That's great! Why stop the party?

The single biggest reason is that the LLM ran out of easy targets. In the first thirty days, I approved 75% of incoming PRs. In the latter thirty, that number dropped to 30%.

The theoretical underpinning of the whole enterprise is that there's a sweet spot: the risk of a given PR has to round down to zero, while the value of the performance benefit has to stay high enough to outweigh the attention and energy required to review it. 3This will be covered in a post to come, but a note I'd have here for the "get rid of code review" maximalists is that at three of the PRs I rejected would have caused an incident if merged. Without looking too hard at the Insights dashboard, it's clear the LLM ran out of obvious wins and it started getting desperate. Most of the PRs it submitted toward the end were bad code that made choices I didn't like — adding branching logic to defer work under some very esoteric circumstance, say, which would have a real positive performance impact and an equally real, and larger, negative technical-debt one.

The second reason is that the LLM consistently overclaimed — both the scale of the improvement it was making and its confidence in being able to make any change whatsoever.

I led with the exciting headline: it cut 25% of our reads. Which is great! But that impressive feat is itself roughly 25% of what it claimed it was going to do. Yes, the math there is not a typo. Largely, I think, this is because we did not — for obvious reasons — give it access to the actual production dataset, only the metadata about it. So it was calibrating a lot of its estimates against synthetic datasets it would conjure up itself, and synthetic data is a flattering mirror.

The combination of the two meant this experiment had crossed from positive value into negative-value territory.

What about upskilling?

I'm entirely amenable to the counterargument that I should treat this as a harness-engineering problem instead: give the model better instructions, or tooling to approximate the prod dataset, or coaching on which sacrifices to refuse. And those responses are correct, in a certain sense: they probably would have resulted in a better signal-to-noise ratio. But they still amount to me spending unjustifiable time on this experiment. It was valuable to me because it was free real estate, so to speak — not because I have a deep and systemic database problem. (Once again: thank you to PlanetScale for making that no longer the case.)

Zoom out further and you arrive at the worry that haunts everything shaped like this: there really is only so much low-hanging fruit. Every time a frontier lab ships a new model your proverbial ladder gets a little taller, but at some point you have to move on from your current copse of trees. Which is not to say ladders aren't useful, only that they're not jetpacks.

(Edited and added on 2026/09/11.)

Fred writes:

I think your approach would be great to automate SLO bootstrapping. You could track acceptance rate and stabilize the SLO once acceptance drops, and then only invoke the agent on breaches. Should scale across monitoring a large number of things for non-regression.

(For the unfamiliar, Google's SRE workbook has a good primer on implementing SLOs.)

I like this for two reasons:

1. It gets rid of the daily trigger. Invoking something like this as a daily cron is a kludge — an admission that plucking all of the low-hanging fruit at once would be onerous to the point of disqualification. Choosing a daily cadence is the equivalent of running a migration that backfills on read rather than rewriting the entire table in lockstep: technically janky and slow, but a totally valid approach. Once you finish the backfill, though, sticking to that cadence makes no sense. Far better to have the agent fire when CPU is consistently over a given percentage, or read volume is consistently over a number we define — which is to say, only when there's something worth fixing. (That drop in acceptance rate from 75% to 30% was the backfill finishing; I just didn't have a better trigger to switch to.)

2. It's more portable into other domains. The most obvious — one I've already done manually, and so can imagine working well — is speeding up specific CI steps. But running it in a true SLO fashion, with the system watching P99s and availability rather than a bespoke waste metric, is one I hadn't considered — and one I'm now considering quite a lot.

This tool began as a bit of a joke internally. The phrase "StumbleUpon for newsletters" was at one point deployed. It has since become a bit of a tether for me, a splash of water that reminds me of what actual users are up to -- and, just as importantly, reminds me that all the test data and sniffing around for edge cases is nothing compared to the sheer breadth of the UGC firehose. 1(Is that two water metaphors in a single paragraph? Whatever.)

Much hay has been made of the ability of LLMs to sniff out latent bugs lurking within your codebase. But even judging solely on wall clock time, Fable and Astra have absolutely nothing on the efficiency and signal-to-noise ratio of me spamming refresh on /shuffle, scrolling through the page, and jotting down whatever feels odd, broken, or — crucially — just sort of wonky.

Vicki Boykis writes about walking around your app:

More importantly: if you are building an app, you need to also constantly be testing and touching different parts of it to see if the app flow makes sense. Look at the UI dropdowns, try the search bar. Toggle the toggles. How long does it take to load a result? What do the results look like? What colors are the buttons? How do they work on different devices? At different internet speeds? What about your payment gateway? How does onboarding look for a brand new user in North America? In New Zealand? Could you onboard from a fresh device in under three minutes? Do images load from your CDN?

UGC makes this practice both more difficult and more important in that your app is actually two things: the lovingly and painstakingly manicured constructions of the author-facing app, and then the unstructured dreamspace that your users build with whatever tools you're brave enough to give them.

(That's not to suggest the through-lines in Coffee and Cigarettes are particularly subtle. Many are textual: as if the titular motifs and the various displays of vaguely anonymous cafés weren't enough, characters echo other characters' prior lines verbatim, perhaps most obviously and symbolically in the Nikola Tesla line — that the earth is a conductor of acoustical resonance.)

Regardless of narrative structure, though, I found the film straightforwardly entertaining by the second or third segment, once I felt like I had really gotten used to its vibe. (The first segment in particular caught me off guard and suggested a much more surreal film than the ten which followed it.) And from then on out, I started to understand this film to be an exploration — both earnest and comedic — of the ways people try to connect with one another, and the ways people try to seek refuge in consumption, and the overlap of those two things.

I am surprised to discover that people think of this as a boring film, but perhaps that is my biases showing. Most scenes are, to re-use a parallel, like a well-crafted short story: exactly the right length to land the punches they wish to before departing. And I will remember this film more by its trees than its forest:

1. the sheepish way Iggy Pop, after awkwardly dismissing Tom Waits despite their kindred spirit, reaches for a second cigarette, hoping no one catches him doing so;
2. the shadows falling on Alfred Molina's face as he is finally and explicitly rejected by Steve Coogan, both of whom playing fictionalized versions of themselves to great effect;
3. the angelic notes of Janet Baker summoned as if to suggest a bright and beckoning afterlife awaiting the protagonists of the final segment, who, pretending for sport that their coffee is champagne, takes one last celebratory sip.

Conjury exists almost as a perfect distillation of this trickiness, because it is fundamentally a very good iOS game with much to love that — after a while of playing it — I cannot help but find wanting in comparison to its forebear. Structurally, and aesthetically, it is almost like a demake of Slay the Spire.

Each run consists of a handful of acts, shorter and with fewer branches than Slay the Spire. Combat is a simplification of the same engine: using energy to play and draw cards, balancing attack and defense, leaning on emergent interactions between cards. And it is particularly well optimized for its format. It looks gorgeous on an iPhone; the pixel art is done just right, as are the audio and the scaffolding around it.

Where the game struggles, on the gameplay side, is in the monotony — both at a micro and a macro level. In a micro sense, encounters do very little to differentiate themselves from each other; even bosses feel fairly samey, and whatever variety a given fight offers comes much more from the order in which your cards are dealt than from any need to tailor your tactics or decision-making to the enemy you happen to be facing.

At a macro level, the various characters you can play in Conjury do feel fresh and distinct from one another, but repeated runs of a given character do not. This would be much less of a problem if it weren't for the fact that, in order to unlock new characters, you have to grind through a lot of runs. Where Slay the Spire is very generous with handing you new mechanics and play styles and characters as soon as you're ready to appreciate them, Conjury makes the exercise feel daunting and chore-like. In a way — and to its credit — that is not entirely dissimilar from games of the era whose aesthetic it so successfully emulates.

So it's not as good as Slay the Spire. Is that so brutal a condemnation? No.

And, to end on an earnest and positive note: the more honest comparison would be with other iOS games, where all of my quibbles are rendered moot. I don't think it's unreasonable to say that the average iOS game ranges somewhere from offensive to actively malicious. Obviously, there are many counterexamples. But if you're evaluating this game from the perspective of is this a better choice than anything else on the App Store, given that I've already played Slay the Spire to exhaustion?, the answer is an emphatic yes. Hmm.

Playing — and ultimately washing my hands of — Soulstone Survivors felt very much like this. Not because of anything so simple as in-game quality: the game is a competent, polished entry in the survivors-like genre that Vampire Survivors spawned into existence, one of many that focus on polish and technicolor spectacle.

But one of the things I think is underrated about Vampire Survivors' success is that it's a weird and charming game, filled with secrets and surprises meant to confuse and delight the player — not merely to accelerate the rate at which dopamine enters the body.

Soulstone Survivors is very good at the dopamine. It is also, in a certain sense, very boring. The game offers breadth — skill sets, customization, playable characters galore — and these choices do have meaningful differences. But they all serve exactly one purpose: to explode things and clear fairly simple arenas in a manner that does not vary from run to run.

It would feel disingenuous to give Soulstone Survivors a particularly negative review, because it is a fun game for a time, and it accomplishes exactly what it sets out to do. And yet I can't recommend it — because I don't think it is good for you.

I am, at heart, a romantic who believes that video games are, at their best, a transformative piece of art. Even the ones focused purely on pleasure can do so nobly, in a way that puts them on the same tier as something like Ocean's Eleven or Jaws: works of entertainment that carry merits outside that simple rubric. Soulstone Survivors is not one of those. It is an M&M.

More seriously: I'm excited to see the reduced cost, but have a very hazy time of describing the shape of work that Fable 5 was unable to complete, which is not to say that it didn't exist, but that it's hard to even conceptualize a step function improvement because the line between "LLM can do this" and "LLM cannot" feels so amorphous. I suspect their lack of concrete examples here is proof that this is a broader issue.

Later that afternoon, I fired up 5.1 in much the same way I had fired up Fable 5 for the past few weeks, both on Conductor and, an hour or so later, on the Claude Code webface.

When I fired up the webface, it prompted me -- in a full-screen modal dialog -- to try out Fable 5.1, even though Anthropic had all the information it needed to know I had already tried it out.

Then, later that evening, I wanted to look at one of the long-running tasks I had kicked off before leaving work. So I opened up Claude on my phone, at which point it announced -- in a full-screen modal dialog -- the release of Fable 5.1.

The two options to dismiss this dialog were "try it now" and "maybe later."

This little papercut is not novel in any sense: it's happened for every model release from Anthropic in recent memory, and is a common genre of problem across all sorts of applications.

Anyway: Fable 5.1 seems good. It is faster and cheaper for the work I've used it for than Fable 5. And I am quite confident that someone could probably feed it the contents of this blog post and it would fix the issue I am whining about. But every time I hear a frontier lab employee mention that software engineering is a solved problem I pretend they say that cooking is a solved problem.

Everybody Wants Some!!, conversely, generates pleasure as sheer by-product of its subject matter: what it's like on your first few days on campus as a freshman in college. Because those days are glorious and orgastic, so too is the feeling of watching the film; everything that the film is interested in conveying emotionally is downstream of its loyalty to conveying earnestly, as is often the case with Linklater.

The extent to which you find it legitimately a great piece of filmmaking (as everyone agrees that it's a fun time) is based solely on if you find its script earnest rather than hedonic. The highest praise I can give it is that my sensation upon watching it — first ten years ago, and then again today — was a resounding "yep, that's exactly how it felt." I went to college in 2009; I did not play for the baseball team; but I can still remember that exact sense of heightened reality that suffused my first few weeks of college, and it felt the exact same as watching this movie feels.

In this respect, it shares for me an unlikely honor with Donna Tartt's The Secret History, another piece of art which was almost entirely an act of memory-keeping by its creator about their undergraduate experience, and which I found spiritually resonant in a manner unlike any book about "being in college" before or since.

Linklater touches on a lot of aspects here, but the one that hits home for me the most is lampshaded by an exchange between our protagonist and Glenn Powell, in what ends up being his breakout role as Finnegan:

In Linklater's memory of college, the identity of the individual is thin and negligible and therefore mutable. What matters and what persists is the identity of the collective. Everyone can put on cowboy hats, but they'll still present themselves in exactly the same way.

(To the extent that I have any critique of the film, it's that Linklater is almost heavy-handed with a lot of this. I guess he feels the need to balance out the joy of the film with a bit of didacticism — no more evident than in the climactic final-night party of the day, a literal costume partty.)

Almost all of the performances in this film are great and lovely in their own way, because they match the specific version of the character they're trying to portray.

But there are two people in this film who deservedly became stars: Glenn Powell and Zoey Deutch, both of whom are not only unfathomably charming in the same way everyone from college is, but also sell their magnetism in a way that reminds me of the most charming people I knew in college: people whose air I was desperate and grateful to share.

This film ends with a scene and message as cloying and obvious as it is lovely: a professor writing on the chalkboard, the first day of history class: "Frontiers are where you find them."

To me — someone who spent most of his time in college in some brew of both proactive and reactive self-discovery and self-reinvention — this gets to the heart of the specific kind of experience being a freshman and an undergrad provides: a fractal sense of wonder in all the uncharted territory.

And now, more than a decade after having left campus, it is clearer to me than ever that success in my four years there can be measured — or perhaps divined — by the extent to which I felt comfortable surrendering myself to the act of discovery. Is this, perhaps, what Linklater is trying to say? More than anything else, experiences are shared, but discovery is private, and the joy in college is that it forces you to understand that you can't have one without the other.

BB is a tool from the folks who built Terragon. The illegibility of its value proposition over Conductor — which is still my day-to-day development environment of choice — was overcome by my goodwill for those folks, and for how much I enjoyed Terragon in its too-brief existence.

BB's core conceit is that the customizability of the tool itself is given priority: rather than shoehorning yourself into the same UI, chrome, and workflows as everyone else, you can ask an LLM to essentially build it on your behalf. One might argue that such a thing is already possible, given how extensible VS Code is — just with more steps. But that does BB a disservice. There is something meaningful about a product choosing that, specifically, as its North Star and prioritizing it as such. There is something akin to emergent gameplay in giving developers permission to really iterate on their mise en place in a way that other tools do not.

I was impressed with BB, but I did not use it for more than a few days, even once I got into the swing of it. Because — and this is no fault of the app or its intentions — it makes the opportunity to snack so tempting. I realize, in hindsight, that I spent more time futzing with the chrome and seeing just what I could do with the tool than I did actually using it to deliver and build things of value. And what's more: the feedback loop, and the feeling (as my friend Myles says) of viscera that you should have with your product, is instead replaced by that same feeling toward the tool you use to deliver the product.

I don't have a good sense of what BB's future holds. I think it's cool, and I'm glad it's open source. And, like many things, I hope I revisit it in six months to discover that its progress and mine combine to yield something of legitimate value.

Grok Bot has done the impossible: it has forced me to acknowledge the Grok brand — a branding decision so viscerally bad, so painful, that it makes the shift from Cheetah to Composer look mild by comparison.

On paper, Grok Bot does many things I don't like. It encourages anthropomorphization. It provides value through crons and periodic work that are kicked off unattended and hard to observe or monitor without deliberate effort. It obfuscates the distance between how you interact with it and what is really happening. But none of this really matters, because — as many people have said — it gets a lot of ineffable things right. And, thankfully, the value it represents has nothing to do with what I find particularly odious about it. 1I am very, very confident that every single other frontier lab will launch something similar by the end of September.

The iteration that Grok Bot represents over the current suite of LLM tools is summarized neatly by a single fact: when onboarding or using Grok Bot, you are never prompted or asked to choose which model or reasoning level you want to use.

In stark contrast to BB, I have spent exactly zero time futzing with Grok Bot. I have not had to help set up its remote execution environment, or deal with permissioning, or any of those things. It simply gets out of my way and does some of the annoying things for me, like resolving trivial merge conflicts.

I will submit as my defense a certain kind of subconscious aversion to anything under that curfew. In much the same way that I have largely exited the world of fintech after Stripe — with the notable exception of fervently checking for updates about the growth and progress of FedNow.

All of this is a lead-up to say: I had reason at my day job, thanks to Steph, to try generating an EPUB file from Markdown source. An idea to which I said, "Yes, how hard can it be?"

Usually, when I say that, it is a prelude to disaster. But in this case, EPUB turns out to be pretty nice and simple. So I am going to drastically sand off the edges of some of the complexity, because I think the core bit is what's important:

EPUB is a zip file that contains some metadata files and a bunch of XHTML. That is all.

This was delightful as a discovery and disastrous as a derailment, since now I'm going to use that as license to spend some time — just like I did when I did my deep dive into ICS a while back Are calendars underrated? — to daydream about some features that might be frivolous and unjustifiable, but nonetheless fun to take advantage of.

The film is never weak, but it is weak for Hitchcock in parts. Watching it for the first time, and knowing that it is a Hitchcock film, you feel as though you don't quite need all the foreshadowing and lampshading. As it progresses, you can't help but feel a sense of déjà vu with his other work — remarkable for this film as compared to the parts of his filmography not considered his absolute best.

As a remake of his own 1934 work, and something relatively mid-career for him, it is very much him in his bag, doing what he does and what he is well known for. Compare this with, say, Family Plot, where your mileage largely depends on how willing you are to go along with him doing something much shaggier than usual. Put another way: this is the first Hitchcock film where I found myself not once, but twice, checking how much time was left in the movie and being surprised that there was so much still to go.

But those dizzying heights. There is, crucially, the ability Hitchcock has to wring noteworthy performances from the Jimmy Stewarts of the world — to see something new and interesting in a face you have already seen so many times. I say this without consulting any of my prior notes, but my gut reaction was that this was my favorite Jimmy Stewart performance I have ever seen. He plays a man who fits perfectly the definition of fumbling.

Hitchcock uses his frame for great gags, especially in the first act. But there are two scenes in particular where you see Jimmy Stewart as something an actor of his caliber is almost never shown as: a completely broken man. First, the close-up of him holding the corpse of a dying man, trying to process on many levels the mistakes and errors he has made over the past few days. And then a scene that is grotesque in many ways, but not unrealistic, when he coerces Doris Day — his wife, who must be said is consistently much smarter than him throughout the film — to take a fistful of tranquilizers before he delivers the news that their son has been kidnapped.

For all the love I have for Cary Grant, he tends to have a certain problem in Hitchcock films of being too starkly charming in the scenes where terrible things have happened to him. Jimmy Stewart crumbles, and stays crumbled, until the very end.

And then, of course, there is the VistaVision and the scene work. I am not smart or well versed enough to talk about the technology and how Hitchcock used it, but the aesthetics are perfect and gorgeous. He relies a lot on static shots, especially when we are first introduced to Marrakesh, that — like a discordant note held for slightly too long — usefully upset the viewer.

But where I must end this review is, I imagine, with the set piece that most people think about when they think about this film: Albert Hall. Five minutes of opera and those aforementioned static shots, not a single line of dialogue, but stress building and building and building — for me, it is indelible, and so powerful that even after I forget the silly international spy bits, I know I will remember it for years to come.

I think this is correctly placed in the mid-tier of Hitchcock's canon. His best films are tauter and have more things to say, tauter and carry more opinions than this one does. But a middle-tier Hitchcock film is still a very good film. And if I got to watch something this good every evening for years to come, I would consider myself a very lucky filmgoer. 8 out of 10.

One last thing: Doris Day was great. The script did not really give her much to display any sort of range, despite the character herself being very competent and capable and, again, much smarter than Jimmy Stewart's — but there's just not a lot for her to do. 1Honestly, the same could be said of Jimmy Stewart's character, and to a certain extent that's why parts of the film drag as much as they do: you get the sense that our protagonists are, up until that Albert Hall scene, passive observers more than they are agents of the action. Not a sin in and of itself, but it exacerbates the drag in the middle of the film, because everyone is just going through the motions. But Day's performance in that tranquilizer scene is unimpeachable — and, as with Jimmy Stewart, not something you're used to seeing from an actress of her stature.

I was wrong, obviously, and I loved it. I loved it in much the same way I loved They Came Together, which is essentially the same film with a slightly different cast. Where They Came Together skewered rom-coms, this one makes fun of teen movies. These films are not well-reviewed in the same way a particularly good episode of Saturday Night Live in its heyday would not be well-reviewed: part of the appeal is vibes and volume. It is easy, perhaps, to focus too much on the jokes that don't land, as opposed to the ones that do.

For my part, what the movie feels like is a warm hug. And in a strange way, it gives me the sense of having already watched it many times — this first viewing being the latest in an ongoing series. Not because the jokes are stale (though, having spent enough time internalizing the UCB extended universe, you could certainly make that accusation) but because it feels comfortable.

Obviously it is fun to note, as many people do when discussing the film in retrospect, how many incredible stars — or if not stars, then guys — are jammed in here. But I'll avoid saying too much about them, because I don't have much to add that hasn't already been covered at length. I do want to give specific accolades to the children, who managed, in scene after scene, to just absolutely nail the assignment. This is not easy work, honestly. A version of this film in which the child actors drag down the whole thing is not far-fetched.

Is this the greatest comedy movie ever? No, obviously not. But it might be the one, in some small way, that I'm most grateful for — both as a kind of beachhead for a bunch of very talented people to go on and do other things, and as a sort of rallying flag around which people can organize.

The UX is very simple. If you have a domain backed by Cloudflare DNS, and that domain runs through a DNS proxy, you can put a one-click authentication wall in front of it. Delightful.1Free up to fifty users, at which point it's seven dollars per user per month — worth knowing before you wall off something with a big team behind it.

Obviously, this is not useful for everything, or even for most things. But we found two good use cases. The first is our admin site, which obviously needs to be protected — but doesn't need a broader authentication mechanism, or any real knowledge of a user model. The second is our internal tooling. We have an internal file-sharing tool, for instance; putting it behind the same access policy isn't a game-changer, but it's genuinely nice, and it's genuinely neat.

What I admire most is that it feels like an obvious case of vertical integration used for good. I think that's very cool. It gives me a glimpse of a world — perhaps not too distant — where Cloudflare is a much more serious contender in infrastructure. Which is not to say they aren't already one.

If you squint a little, there's a lot of tooling and adjacency that becomes much easier to build and sell once you already sit on a user's DNS. Historically, the answers have been kind of boring: email, web hosting, and so on. But with sufficient skill and ingenuity, that's just the tip of the iceberg.

The biggest downside, obviously, is lock-in — to which I have no salient or interesting answer, besides that the switching costs of using such a service are outweighed by the utility it provides. That could certainly become untrue in the future. But it isn't today.

I'll admit that I'm more of a Chekhov man than an Ibsen one, but so much of what I loved about Vanya was not the script or the play itself; it was the interplay between the idea of theater and the idea of film. Vanya suggests a synthesis of the two forms through a shared goal of enchantment; the performances are great and the material is great, but all the fourth-wall stuff is meaningful on a level beyond devotion to the play itself.

A Master Builder comes two decades later, directed this time by Jonathan Demme (of Stop Making Sense and a slew of others.)

Demme appears to be going for something quite different -- or at least achieves (though that implies a certain intentionality) a much different effect. A Master Builder feels less like a sequel to Vanya and more like a spiritual rebellion against it: naturalistic performances are replaced with exaggerated ones; calm, steady, invisible direction is replaced with jarring cuts and off-putting close-ups; the warm, decrepit charm of the crumbling playhouse on 42nd Street is replaced with sterility and cold tones. Put simply: Vanya wants you as close as possible, and A Master Builder is insistent on pushing you away.

And consider myself pushed! There were more than a few moments during this film where I felt uncomfortable — not because I was grappling with something difficult, or reckoning with what the film was trying to tell me, but because everything simply felt so jarring in a way that seemed poorly architected rather than intentional.

(Hagerty was great, though.)

Update. My friend Jennifer emailed me to suggest that I listen to the Blank Check podcast episode about this, and as someone who only has room for one middlebrow film podcast in their life, I had been putting this off for quite some time — but I'm glad for her suggestion, as I finally took the plunge.

Not only because it was a very funny episode in which I had all of my priors confirmed, albeit in a more manic and eloquent manner than above, but because — of all people — their guest was John Hodgman, who delivered this point about both the play and the production altogether:

But only do I feel like Julie Haggerty really figures out what this is about when she says the thing. Yeah, my twin children died after this fire. My house burned down that I grew up in. But that's not what bothers me. What bothers me is the loss of all of the dresses that my mothers and grandmothers made, all this silent secret work that women do that never gets celebrated by putting a wreath on a phallic symbol or whatever in the middle of town. And two, these dolls that I had, these nine dolls that I even still as an adult played with these dolls when you were a grown up. She had a secret in her life that got burned up by her husband's ambition. It was just – that was the moment where I felt like, oh, this could be a – you could redo this play and it would be revolutionary to see today.

1. it is short,
2. it is nuanced; he is clearly neither arguing that technical debt is a thing of the past and we should treat it as such, nor that it's the exact same as it's always been.

With that in mind, I have four commingled takes. 1Thank you to Sonny who reminded me that I cannot count.

Technical debt is materialized as drag against the ability to deliver customer value.

This sounds like a pedantic recharacterization of Jesse's words, but I want to be very deliberate about this because I think the distinction is meaningful. In particular, it is important to remember that there are times where the technical debt brings pain even though we're not trying to make a code change or deliver value through a code change. If there's an incident that takes 2x as long as it should because nobody knows how the relevant subsystem operates, that is still technical debt.

If you would like to argue that that gets materialized purely as bad documentation or some other failure, okay, fine, whatever. But then the question becomes: how do we more adequately build LLM-generated codebases which humans can operate and internalize the mechanics of just as well as their own? I don't think we have arrived at that answer,

LLMs are default net-producers of technical debt

I am a person who abhors technical debt, often to the detriment of my ability to build more directly useful things for customers. I feel fairly proud of my ability to leverage LLMs to drive down technical debt. There is no question that Buttondown's codebase is filled with less technical debt than it used to be, even though it is more generated by LLM than it used to be. However, that's not happening a priori. If I were to ask the Council of Frontier Models what specific things I could do to lower technical debt, their answers would be incorrect and would probably end up increasing technical debt. (This harkens back to one of my favorite aphorisms, which is that technical debt is the delta between a codebase and the reality which it attempts to map.)

I have seen enough codebases from organizations and individuals who do not care about technical debt to know that, absent very strenuous guardrails and intervention, the situation gets dire very, very quickly. This is a problem exacerbated by the fact that observability tooling for LLMs is still at a very nascent period, such that we feel the pain of technical debt without being able to quantify it. When you are spending all day struggling with some bad abstraction or kludge, you notice and internalize that much more than when an LLM is.

LLMs are not free

In a world where technical debt is completely solvable by LLMs, all that means is that the technical debt now assumes the form of traditional financial debt. LLMs are not free. I know it's really boring to say that, and I don't mean it in any sort of doomerish way. The thing that frustrates me about the school of thought that with enough tokens you can solve any problem is that, like, yeah, man — the tokens cost a lot of money. I think this is important to remember because suddenly we will want to reason about this work financially and not just from a productivity perspective. Certainly, I have been evaluating my own tool usage with the end goal of driving down cost, driving down token spend — which is technical debt in its purest form, if you can approximate token spend as a rough proxy for knowledge-work-based labor.

LLMs devalue features at the same rate they pay down debt

Jesse ended the post with a supposition:

[If you think LLM improvements continue to compound relative to consumer price], you should probably spend less time worrying about tech debt, and spend more time shipping new features.

I think this is true if and only if you are in a position where there's genuine first mover advantage and you happen to be that first mover. Otherwise (again, given this supposition) you must assume that your competitors are reasonable people who will be using these tools too, and therefore also pay down all of their tech debt and ship all of the features. The Red Queen problem comes for us all!

Personally speaking, though, I have learned to grow suspicious of prognostication that lets me lean into the kind of work that is easy and fun.

As I wrote in Snacks are cheaper and tastier than ever, I think you have to spend some time thinking really hard about what is the most important, highest-leverage use of your time — whoever you are — and changing your habits and approach to engineering accordingly. Regardless of the future of LLM capability or cost, I think the relative margin in having a given feature goes down for the simple reason that marginal cost of implementing that feature has gone down.

So this essay ends the same way all of mine lately: you need to find durable and meaningful ways to create value for your users. Same as it's ever been, but more so.

And I feel comfortable with that because gaming is a different experience and mechanism than consuming literature. Books, generally speaking, are about the gestalt, and it is hard to opine on the full quality of one without knowing how it ends, and the feeling that comes over you when you close it and sit with your thoughts. A game, conversely, can be called a success if it entertains you meaningfully and deeply for some portion of time, even if you put it down while there is still content left to experience.

So I am breaking with tradition here. I am talking about Secondhand Time, my favorite book of the year — a book that has taken me six months to get through and will probably take me another two or three to complete. And I am comfortable talking about it because, not unlike a video game, it has already offered me so, so much, that to delay doing so would be an exercise in unnecessary formality.

Secondhand Time is an oral history of the regions comprising the former USSR, compiled almost entirely from firsthand narrative: actual people recounting their past. It is sprawling and nonlinear. There are obvious messages the author is trying to communicate — but unless I am in for a rude awakening, there is going to be no denouement that deeply recontextualizes or reshapes everything that came before.

You hear countless stories, repetitive and rhapsodic, from every possible walk of life, though almost all of these walks involve the scars and bruises left by war and revolution. The only unifying thread is sadness and bitterness — not nostalgia, though certainly some of these stories contain nostalgia, so much as the sense of a country weeping for all the pain it has gone through.

It is a brutal and beautiful book. It has taken me a long time to read because, frankly, sometimes the brutality — the extremes of the human condition to which I have been so privileged to be largely ignorant — is too much to bear, and I need to wade back out into the shallows until I am ready to resume.

This is an oral history. And at the time of this writing, The Odyssey is the single biggest movie event of the year — The Odyssey being a book that is the writing-down of a story told from person to person over many, many years. And that story, too, is about a man who primarily tells stories: to kings and gods and everyone he encounters, sometimes for good effect and sometimes for ill.

I am drawn to the comparison despite these two books sharing little to nothing with one another. Let me give you one example.

One of the early stories in the book is about Sashka, a man who burned himself alive in the vegetable patch he owned outside a barracks — a suicide, to escape the pain of his daily drudgery. The story is told to us through by the author, recording faithfully the words of Sashka's friend and neighbor in the barracks.

That neighbor spends her time on the page filling it with wild digressions that the author clearly found fascinating enough to include, and she was right to. One of these digressions is about the neighbor's mother, and the time the Germans occupied their remote farm town. In the span of a single afternoon, they shot every single Jew in the whole town. Except — the speaker tells us — two frightened and clever little boys, eight and ten years old, hiding out in a neighbor's barn.

Her mother, one of the few in on the secret, was tasked with bringing these precious children a little milk in the dead of night whenever she could. But because in such stories there is always a turn, after a week or two she awoke to the screech of three German motorcycles pulling up to the barn. Someone else, it appears, had told a story — had informed on the barn's owner, fabulizing in the process, saying it was not just two boys but an entire dozen of Jews hiding. The two boys were shot immediately. And the neighbor, for all their bravery and trouble, was tied to one of the motorcycles and forced to run alongside it until their heart burst.

I think, right now, for one reason or another, I am drawn to things that try (in vain, with honor) to evoke the sheer depth and breadth of the human experience. Ducks, Newburyport was the last book that took my breath away in quite this sense — a feeling that can only be described as transportative, a sense not of enchantment but of teleportation.

It is a blessing to get to read something like this. It also requires not just fortitude but reflection; I have put down this book for an afternoon and felt myself so compelled by what I was reading that I knew I had to start writing about it.

This is not an obscure book. The author won the Nobel Prize. And yet I have never heard anyone discuss it. Perhaps this is due to its peculiarity — its sitting outside the easy confines of genre, neither a traditional history nor traditional fiction by any means. Perhaps partially due to it being a Russian work, though it must be said that the English translation is masterful. Perhaps due to the book simply being uncomfortable and unapproachable.

The stories of triumph and victory, rare and fleeting as they are, always arrive as either a prologue or an epilogue — which is perhaps the most honest way to think about the human condition. Narratives ought to impose a clean chronology on events: a rising action, a falling action, a denouement. But this is never how the world works. And to the extent that we can feel comfortable with the illusion — whether in our media or in our day-to-day lives — that comfort is equal parts blessing and willful ignorance, handed to us by many people, almost all of whom died and suffered in life, whether on the battlefield or in the factory line.

This is one of many decisions that makes Letterboxd a fascinating and well-designed piece of software, because I have no idea how to rate MacGruber, which strains the conceit of a single numerical score. And I don't mean this only in the same way it can be said of all comedic films. Obviously it is harder to discuss the positive and negative qualities of comedy as opposed to drama, because subjective tastes become even more subjective.

But very specifically, my reaction upon watching MacGruber — a film during which I laughed out loud more than any other film this year — was some combination of "that was a piece of shit" and "I wonder if these five people have seen this, because I bet they'll love it."

MacGruber does not satisfactorily answer the most important question an SNL film must answer, which is: why does this need to exist at all? You could, again, say this of any work of art, but SNL films are all of a kind — sequels to sketches whose idea was already hyper-optimized for a medium much, much shorter than ninety minutes.

One answer might be this: the writers 2The credited writers are Forte and two SNL writers, which I would surmise is metonymy for "the SNL writer's room." had a handful of ideas stuck in their heads that would otherwise not come out. In the process of building a low-quality movie, they spilled those ideas, and it turns out some of them are extremely funny. Another answer might be that you give the late, great Val Kilmer and, of all people, Ryan Phillippe a chance to play opposite a character who — in a film or in a skit — is so loud that others do not have the budget or the time to do anything except react in a quick reaction shot. (Both, of course, are true yet insufficient.)

And the film feels, quite vividly, like a college dorm room filled with jokes and half-jokes being hurled like careless javelins. 3This is a connection I draw with no bias, even though it was released in 2010 while I was an undergrad. There are lots of jokes about dicks and balls. The repetition of these jokes itself becomes a joke, and it lets you briefly — for a fraction of a second — pretend that it is elevated material. If you don't like a joke, don't worry: another one of varying quality is coming five seconds later.

What else is there to say? This is not, to be clear, elevated material. But I can't imagine a better version of MacGruber than what we got. And the one we got made me laugh a bunch. Not just for obscenity's sake — because in the midst of the detritus, there was some really good material. Truth be told, I am not that much of a Will Forte fan. I would consider myself more of a Jason Sudeikis guy. But his comedy — and, as getfiscal puts it, "pure energy" — evokes in everyone he plays opposite who isn't from SNL 1Wiig really doesn't do it for me here, with a brief exception of her disgruntled face at the prospect of having to pretend to play the titular character. a certain blessed mania.

Guildrun is a single-player auto-battler in the spirit of Teamfight Tactics. If you're unfamiliar with the genre: it revolves around setting up a roster of heroes, equipping them with skills and items, and then having them fight against increasingly difficult enemies while you watch. I have never been a huge fan of the genre, and yet Guildrun has completely ensorcelled me — in no small part because I think they have nailed the balance between mastery and chaos. There's enough randomness in a given run that each one feels different, but I as a player have enough agency and optionality to feel that my choices not only meaningfully impact the run but that I'm getting better at making the right choices over time.

This post isn't really about Guildrun, though. It's about their patch notes.

Remember: this is a demo. The game is not yet out, and it is a single-player game — there is no ladder, no economy, no opponent whose feelings about a nerf you have to manage. And yet the notes are uncommonly detailed and well-reasoned. It is very hip to talk about the lessons application designers can learn from game design, largely around progressive disclosure and activation/habit-building. But the thing that caught my eye here was how the balance dev talks about archetypes of players, and how they weigh priorities when making changes.

Since it just isn’t possible for every player to be happy with every decision I make, I try to think about each decision in terms of the “net fun” it will add to the game for each kind of player. I read through my list of changes from the perspective of each major player group, then add up the total amount of positive and negative “fun units” I expect these players to derive from each change. This way, even though certain changes add to the net fun of one group while subtracting from another, I can always aim for each player group to end up with a positive net fun score, which hopefully translates to a positive view on the patch. However, if even one player group ends up in the net fun negative then I haven't done my job well enough.

For Guildrun, the 3 major groups of players are the Climbers, the Endless Mode players, and the Red Rift players. The Climbers are players who are in the process of climbing through the difficulties to unlock and complete all of Guildrun's content, and are currently our largest group of players by a decent margin. Everyone starts out as a Climber, and for many of these players the quest to discover everything the game has to offer is the game. The experience that players have during their climb through the difficulties is incredibly important to us, and the feedback from Climbers helps make the game better for all Climbers, present and future. Since the primary goal for most Climbers is to progress up the game's difficulties, it's easy to understand why nerfs can feel like an obstacle standing between them and their goals, and why buffs feel like a helping hand.

It does not require a lot of rhetorical justification to understand how this might apply to traditional software. Software tends to grow more complex and featureful over time, which rewards edge case users who have already onboarded at the expense of new users; conversely, redesigns or radical simplifications of an interface might be a net positive for new users without any muscle memory whatsoever, but are often experienced as a net negative to experienced users who log in to find that all of their cheese has been moved.

Even more than that, I find, as a player who now aspirationally describes themselves as in absentia from any sort of impact of these notes, I can't help but admire the thought that went into these changes, minute as they are. And the explanations themselves, even if I might disagree with them, generates goodwill towards the organization, because at least now I can understand that there was a thought process and not just whimsy

The worst thing a piece of comedy can do is, in the process of not taking itself seriously, forget to take its characters seriously. This film is deeply funny, and deeply weird, but Kaufman remembers every step of the way that these people are real, that they want things and feel things. (And I'm sure there are a lot of interesting things it's saying at a metatextual level, but I figure I should finish watching Adaptation before I mull on those too heavily.)

And now, having finally watched Adaptation, I feel as though I can adequately comment.

This is the first Kaufman film that has left me with a lesser level of respect for him than before. It has moments of greatness, many of them not owing themselves to the script. Streep's performance, both comedically and somberly, is brilliant — a couple of shots of her transfixed in thought, in particular the scene where she watches Laroche make a sundial (or the moment a few minutes later, when Charlie runs into her in the elevator and does nothing), are singularly devastating in a relatable way. For who amongst us has not had a tiny little non-incident in passing force us to zoom out and realize that we are standing in a swamp?

Some of the production gimmicks, especially in the film's first act, are fun too. And while it's not exactly high cinema, I think Nic Cage acted well enough to earn the gimmick of being billed twice.

But outside of the performances and a couple of particularly good shots, the film is juvenile, both in a straightforward way (lots of objectification, lots of the word "fatty") and an existential way.

Take a film that more people have strong takes about: Everything Everywhere All At Once. Detractors of the film will argue that it sacrifices substance for style; nobody would argue that it's not trying to deploy its style for the purpose of its emotional arc, just that it is unsuccessful in doing so.

Adaptation, conversely, is clearly about passion and the creative process — but its underlying structure undermines its ability to concretely say anything about these topics beyond the fact that Charlie Kaufman spent some time thinking about them. (Perhaps we can credit Kaufman with the invention of irony poisoning!)

Bringing up EEAAO also reminds me that much of my 2026 viewing of this film is tempered by how far we've come creatively in the two decades hence. Lampshading (a la Brian Cox's screenwriting teacher) is now old hat; recursion is seen in all media, because we have a stronger understanding of how all media is recursive. But this is not the Velvet Underground: Adaptation might be early to some of these things relative to mainstream cinema, but it ultimately relies on novelty and audaciousness (and a hope that you'll find it sufficiently clever) to be worth seriously recommending.

Let me end on a positive note, which is Streep's final line reading and the best I've heard all year:

It's over. Everything's over. I did everything wrong. I want my life back. I want it back before everything got fucked up. I want to be a baby again. I want to be new. I WANT TO BE NEW.

The two parallels that come to mind — less in terms of style and message than in terms of how one situates the prose — are Murakami and Woolf.

Murakami is, to be clear, the much less stylistically successful of the two. But like Murakami, Lispector's work has been treated with a sense of otherness — not as a method of denigrating it, but to suggest that it sits outside its country's literary tradition. And while you can make a compelling argument that Murakami taps into a distinctly Japanese sense of alienation and ennui in the modern era — and, moreover, that much of his earlier writing is explicitly political — Lispector here is ethereal, barely attempting to give any hint or indication of where and how her protagonists live.

Part of this otherness — the sense of the story being completely untethered to any semblance of setting — serves contemporary reading well, in this age of autofiction and, for lack of a better term, idealistic narcissism. There is hardly a hint of whiplash going from Ben Lerner to Lispector.

Woolf I evoke for a handful of reasons. First: like Lispector, Virginia Woolf is often praised backhandedly, under the umbrella of feminist literature, or feminist modernism. But Woolf's goals — say, in To the Lighthouse — are directly oppositional to Lispector's. The Lighthouse is an argument toward the permeability of consciousness and shared existence, conveyed with empathy and perspective. Woolf uses the frame of modernism to talk about shared experience, and this pattern forms a lineage in which I can find much of my favorite writing. (See also A.S. Byatt's Possession.)

Lispector, conversely — at least in this book — is a solipsist. Her self-insert protagonist is the raison d'être of the entire prose, the sun about which every other character orbits. Any character not named Joana is given time and energy only insofar as they shed light on Joana. And the philosophy of the book — beyond its explicit cribbing of Spinoza — is an argument, if not quite in favor of this, then against the status quo that spawns it.

All that aside: this book makes me more intrigued to read the Lispector of her later years, while considerably less excited at the prospect of having found an author I can spend the next decade absorbing. Her biggest asset on display is the prose. Even through translation, her writing is beautiful and serrated, while never being Rococo. And considering her age upon writing this — and this is where the Woolf comparisons begin to feel unfair — one gets the sense of a young master in full control of what she wants to say and how she wants to say it, but who unfortunately does not yet have much at all to say.

One last note: the final chapter, a series of monologues from Joana, is indeed placeable among the highest echelons of modernism — beautiful and cryptic and self-indulgent all at once.

1Password CLI

A long-standing annoyance has been dealing with secrets and coordinating their rollout across CI, plus a bunch of Heroku instances, plus a bunch of Vercel instances, plus maybe a local box if you need them for critical debugging.

Historically, we did this by using whatever was in the production Heroku app as the source of truth and syncing and linking as much as we could. But with our pending migration to AWS, this approach, which was already crufty, now had two more problems. It had an expiration date, since I believe we are getting rid of the production Heroku app.

And suddenly the number of services to which we need to sync secrets has doubled. Our solution was to do the thing that I always wanted to do but could never quite summon the effort, which was standardize on using 1Password and their CLI. This worked pretty painlessly. We've got a single entry in 1Password that represents all of the environment variables that we need for a given environment and we read from that before deploying. Rolling a key now requires one subsequent change (adding it to 1Password).

mprocs

We've long used Overmind to orchestrate our local dev servers. It is -- was! -- fine, but it carries a steady drip of paper cuts — chiefly the inability to focus a single process's log output and the inability to restart a process from inside the running session. Individually trivial; collectively, hit many times a day, worth fixing.

mprocs is a TUI process manager that solves exactly those. It pages between processes, scopes scrollback to the selected one, and starts/stops/restarts any process in place — no tmux, no external socket dance. After a week of piloting it, we switched over. It's been great.

Best of Enemies, compared to The War Room, has less immediacy and access but much more of a clear agenda and through line. It's about the William F. Buckley–Gore Vidal debates during the 1968 conventions, built out of lots of archival footage with very little fat. We, the viewer, spend more time at the debates than examining them; as someone who confesses to knowing of the National Review, and to owning a half-read copy of Burr, but not really knowing who either of these two individuals were in any meaningful sense — I appreciated how the film is equal parts explanation and analysis.

I hesitate to succumb to instinct and laud both them and the middle-brow public that appreciated and rewarded the idea of intellectualism. The histrionic fondness with which we might remember their patrician accents could very well be said, thirty or forty years from now, of people discovering blogs and pining for the days when public intellectuals would so candidly and openly write on Wordpress or whatever. Additionally, I don't buy at face value the film's thesis that these debates were the birth of American punditry. In no small part because I think television itself was the birth of American punditry — an organism that simply required some time to incubate.

But these two guys are fascinating, and the debates are riveting, and this documentary gets to carry that respective sunlight. The film takes an unflinching look at who these people were and what drove them. How clearly you can see that these two men led twinned lives, to a certain extent: both ultimately failed ambitions, both incredibly intelligent, and — in what seems so deeply interesting, perhaps more so than the denoument of their careers after the debates — both horribly, horribly despondent toward the end of their lives.

As for the debates themselves: it's fascinating to me that it's taken at face value that Vidal won by the TKO of successfully baiting Buckley into an outburst. Vidal succeeded in his goal and Buckley did not, but Buckley knew — as the film references multiple times — that the goal wasn't to be awarded the highest score by the judge, so to speak, but to be known at all.

What is beyond debate (ha) is that the experience destroyed at least some part of both men, or at least revealed to millions a part of them which was rotten.

The final scene in the film is a clip of Jon Stewart appearing on Crossfire, declaring that the format of the show is theatrical rather than analytical: Stewart's appearance was so caustic that the network cancelled the show and the two hosts (Carlson and Begala) considered irrevocably stained by the association: after a decade in the hinterlands (PBS and MSNBC), Carlson was a few years into a Fox & Friends gig as a sort of Barbour-clad ronin; Begala left the television sphere entirely and returned to consultancy.

That was in 2015; in the decade since this film's release, whatever spectre haunting Carlson appears to have vanished, having risen to lead the most popular show on television before his ouster and now in the process of doing the same in the realm of podcasts. Just like sixty years ago, it appears that no transgression can outweigh the power of a sufficiently fervent audience.

If you're in a well-run organization, at some point you're going to run out of things that are both high-impact and easy. This leaves you with a choice between shifting right to hard and high-impact or shifting down to easy and low-impact. The latter choice–easy and low-impact–is what Walk refers to as snacking.

When you're busy, these snacks give a sense of accomplishment that makes them psychologically rewarding but you're unlikely to learn much from doing them, others are likely equally capable of completing them (and for some of them it might be a good development opportunity), and there's a tremendous opportunity cost versus doing something higher impact.

As my role as a founder has shifted to be more explicitly managerial over the past few years, I find myself returning to it whenever I am feeling particularly guilty of the behavior it espouses.

One of the things that has made this much more difficult over the past year has, of course, been the rise of LLMs. One of the things they have done is made it incredibly easy to avoid what Horst Rittel and Melvin M. Webber refer to as wicked problems: problems with no clear success criteria, no right to be wrong, and no prior art (amongst other things.)

A few years ago, I could procrastinate on thinking deeply about go-to-market for a new segment by maybe hammering out a single bug fix or spending an hour in the support queue. Now, suddenly, my alternative to doing deep work contains many new Cyrenaic properties:

1. I can pretend that it is in fact managerial work. Asking Cursor to build a visualization of metrics feels like it is something that is akin to strategy work, even though no decisions were made differently as a result of it.

2. I can build and ship features trivially. And these are features that I earnestly believe are things that, given an infinite time scale, I would want the product to have — even if the reason we haven't built them yet is because it's not obvious how it actually generates leveraged value for the business, nor is it obvious how to prove it.

3. I can spec out and create high-fidelity prototypes for interesting new product directions. Even if those prototypes end up gathering dust, and by the time I'm ready to seriously consider them, the context which necessitated or informed their construction is obsolete.

So what to do?

One answer is simply that I don't know, and it feels very important -- like, "I have written and discarded six other versions of this essay over the past eight weeks" important -- to try and figure it out, because if you have good eyesight you can probably see a Red Queen problem lurking on the horizon where all of the software factories in the world nullify any marginal advantage that the others might have. 1We are far away from this. The median software company, despite what you read online, is still figuring out how to get its CRM hooked up to Claude, but we're not going to be far away forever.

Another answer is "exercise more personal and organizational discipline". This is true but facile.

Here's the answer that feels best right now: the definition of something being done must shift from the code being shipped to customer realizing that. That sounds both abstract and obvious, I know, and I'm sure you can compellingly argue that every good company should already be operating from that position. But this is a personal blog, and in my personal experience, I can say that I've gotten surprisingly far with Budden and other projects, pretending I am Kevin Costner and knowing that if I build it, they will come.

LLMs optimize the transformation of input into output; in my experience, all the context in the world does not aid them in creating customer value from first principles. Now more than ever, the job is to build both wisdom of what users find valuable and knowledge of how to decompose that into legible work.

Here is a baker's dozen of Buttondown's own cursed knowledge: 1Yes, that's the joke.

1. The Python ua-parser library assigns the device family "Other" to every non-Mac desktop browser

2. The HTML accept attribute only filters what the file-picker dialog shows you; drag-and-drop and clipboard paste bypass it entirely.

3. Safari and Chrome re-serialize quoted CSS custom-property strings differently when you read them back via getComputedStyle: Chrome keeps the single quotes, WebKit rewrites them to double quotes.

4. Django emits a CacheKeyWarning — which fails our CI — for any cache key over 250 bytes or containing a space or control character.

5. Python's requests has no default timeout and will, given the opportunity, wait forever.

6. SPF include: directives recursively chain DNS lookups against a hard cap of ten — exceed it and you get a permerror, which can fail authentication for all of your mail.

7. Outlook and Hotmail enforce mandatory TLS but serve a certificate chain rooting at DigiCert Global Root CA (G1) — a root that Ubuntu has since removed from its trust store.

8. Django's JSONField data__key__isnull=True tests whether the key exists, not whether its value is JSON null.

9. UPDATE ... WHERE id IN (...) does not lock rows in the order you listed them — Postgres locks them in executor scan order, which is a wonderful way to deadlock two queries that both thought they were being careful.

10. A postgres tsvector cannot exceed ~1MB.

11. Stripe will send subscription update events for paused subscriptions.

But whether it's due to his relatively short career — made even shorter by his untimely passing — or to the singular power of the performance itself, I could not ever imagine James Gandolfini as anyone other than Tony Soprano.

Having only seen him in one other work — The Death of Stalin, in which everyone's playing a lot of dress-up and having a fun time but not trying particularly hard to be a good actor — I pulled up his filmography and found Enough Said, a film I vaguely remembered, largely for the circumstances of its release. 1Gandolfini passed after the movie had wrapped, but before it had finished editing. So I sat myself down and had a watch, and came away with the obvious conclusion that, armed only with these two performances: Tony Soprano and Albert, a reasonable person would assume that Gandolfini is the greatest actor of all time.

Often, when actors want to play against type, they do so by insisting upon themselves in one way or another — playing a part that seems somehow audacious, or other. Gandolfini here is none of those things. He is a kind guy, but not angelic. He is a bit of a slob, but not disgusting. He plays a human being with depth and nuance and warmth and sensitivity in a way that I don't think I've ever seen quite captured like this.

And that sense could be extrapolated to the film as a whole, which — if you can look past the central conceit and Julia Louis-Dreyfus's tendency to over-emote in the first two acts — is a bittersweet, funny, but deeply realistic meditation on what marriage does to people. Holofcener, who wrote the script, takes no prisoners, but she doesn't cast anyone as demons either. This is a story about two people who are flawed but not damaged. And her writing, mercurial as it is, 2Production notes indicate there was a lot of improvisational work done, which helped contribute to the naturalistic feel — and, in particular, to that final scene. was so good here that I immediately pulled up the rest of her credits to add to my backlog.

The film has its contrivances, and at times forces the point a little too heavily, as if each scene were rewritten to drive Louis-Dreyfus's character one step further into Flanderization. But it is an honest and entertaining portrayal of adults being adults — and when you layer on top of that one of the single greatest acting performances I've seen in my entire life, it's hard not to recommend it. Even if it feels, ultimately, a little slight.

I really enjoyed watching this film, so take it with a grain of salt when I say that it also leaves me a little cold without the aegis of some of the truly remarkable and original shenanigans it pulls off (the details of which I'm being intentionally vague on so as not to spoil anyone or anything). I think the best way to engage with this is less as a film and more as an incredible and hilarious experiment that happened to be released in theaters. An achievement of some kind, if not cinema.

Complaints aside, even knowing what I now know, I think all of our decisions were the right one. Part of this is just getting used to a slightly different status quo. We were able to remediate the two customer-facing incidents of these three very well (thanks entirely to Matias and Steph!), and in doing so, it revealed that we're just missing a lot of obvious kill switches and documentation for failure modes that aren't the ones we've already been scarred by. So a lot of August will be enumerating and addressing those.

But as obvious as it sounds in retrospect, next time we evaluate a new vendor or a new SKU on an existing vendor, the first item on my list is going to be running a script on their status page to see what the actual stability of that SKU is and not just what the reputation suggests.

The soul of the thing is that each media item is a markdown file, just like the posts themselves. Here, for example, is a recent one, for Jay Kelly:

---
title: Jay Kelly
type: Movie
date: 2026-06-30
rating: 5
year: 2025
director: Noah Baumbach
status: Finished
image: jay-kelly.jpg
tags:
  - movie
colorSortKey: [0, 22, 0]
---

> I was young. I wanted something very badly and I was afraid that if I took my eye off it, I wouldn't have it. And I was right. There was no other way to do it. And it meant choosing it over you. But it was always meant to be temporary. Just until I got what I wanted... But then I had to keep it.

I am reminded of the other recent George Clooney vehicle, <a href="/posts/wolfs.html">Wolfs</a>: this is self-indulgent in one dimension, and its merits are almost entirely carried by the efforts of Sandler and Clooney, both of whom give very strong performances which rescue the film from being Bad but do not carry it to greatness.

I also found myself wondering what Baumbach is up to right now. The script and direction here seem entirely *thoughtless* — not so bad as to be offensive, but neither interesting nor characteristic of his earlier and better work. I can dismiss things like the scattershot tone or the half-hearted performances from Laura Dern et al. as being intentional -- it is an ethereal, dreamlike film.

But the movie fails to do what I think it needed to do, which is to make us feel bad -- or novel in _some_ kind of way -- for either character, even if for an instant.

Clooney plays a very light pastiche of himself: if you interpret the film as a story about Clooney himself, you are forgiven for doing so because he so comfortably eases into that role of charm and conviviality. He is a man who made it big, and in so doing had two lovely daughters who care little for him due to his absence -- an absence that he chose, time and time again, until there was no other choice to make.

(And much of the same criticism -- if it can be called that -- can be levelled at Sandler's character, who is a very realistic depiction of a guy worth millions of dollars whose biggest problem is that nobody will say "I love you" to him.)

I watched <a href="/posts/Somewhere.html">Somewhere</a> earlier this year, and I think many parallels (Hollywood people and their Hollywood problems!) can be drawn between the two films, but the success of _Somewhere_ is in what I called "the wattage and nuance of Dorff and Elle Fanning's performances"; both together and in isolation the two performances there stirred something beyond artifice in me in a way that Jay Kelly did not.

---

Lastly, the ending.

I really think the story of this film is that Baumbach — and Emily Mortimer, as co-writer — came up with the final scene and the final line, and then worked their way backwards from it into a movie. And to a small extent, that worked: the final scene, and the final line, cliche as it is, smashes me to bits. But it feels cut from a different movie -- a different life! -- than the one I spent two hours watching.

The front matter is, of course, the most interesting bit to talk about. Most of it is self-explanatory, with the exception of the status, which is what governs the answer to the question: should this be published?

A quick aside on the color sorting. The grid is arranged by the dominant color of each cover, which I extract at build time and cache back into the front matter — that's the colorSortKey field above. It's the one bit of genuine cleverness in here, and mostly it just makes the grid pretty.

Beyond this, every other bit of functionality can be abstracted away into things you can do once you have a JSON blob. The media grid at the bottom of the splash page is just vanilla JavaScript. Deep linking, or wiki linking, to other reviews is handled through a bespoke build-time mechanism — but nothing you wouldn't be able to figure out from first principles, since it's the exact same logic as for how it works for blog posts.

I've iterated on a number of different approaches over what is now, literally, more than a decade of keeping this little library. And if there's one ground truth that I hold dear above anything else, it is the primacy of flat files. They are portable, fungible, and legible.

I lose out on a couple of small idiosyncrasies. For instance, I can't trivially add new things from my phone — which sounds like a pain point, but any solution to the pain point would indirectly induce much more pain than it solves.

In some ways this is Wenders' too-clumsy attempt at combining the two things he loves — the bizarre, met in an ironical register, and an earnest examination of the kinds of people that not just cinema but humanity tends to gloss over. It's a slower film than the rest of his oeuvre, but not by much; there's more propulsive action here than in, say, Perfect Days. Even so, I think it's at its strongest in its first two-thirds, when it is quiet and observational — when we are mostly left to breathe in the space between these two good-hearted angels and the Berliners they wish to help.

The transition into its final act is perfect, even if the final act itself doesn't quite land for me: the fallen angel talking about symbolism, becoming human, immediately getting bonked on the head, the black-and-white exploding into color.

And then there's Peter Falk. His role is so central, and his performance so arresting, that the movie threatens to become his movie — his odes to humanity mirroring Homer's ode to the epic of peace, his monologues as he sketches extras and tries on hats both fun and beautiful. And the dichotomy he provides by giving identical monologues to each angel — the first successful, the second falling on deaf ears — provides a useful juxtaposition.

Wenders' films are content with textual ambiguity but never with spiritual ambiguity; if I wasn't trained by his other works, I'd argue that Falk can be seen more of a Satanic tempter of angels. We leave the film believing that everyone is in their right place: some angelic, and some never happier to have a head wound.

Asking Cary Grant and Ingrid Bergman to both play against type is, I think, laudatory, but their work is half-baked at best. I don't care about their love for each other because it appears as if out of nowhere — a thing the script insists upon rather than something the performances themselves earn. The same can be said of Bergman's backstory as a lush and a "loose woman," neither of which she hints at with anything besides emphatic insistence that she's not that kind of girl anymore. 1Obviously, it is safe to blame The Code for much of this, but Hitchcock does not exactly bend over backward to handle it gracefully.

Claude Rains and his mother — Leopoldine Konstantin in her sole American performance as the stern, vaguely comic Nazi — both acquit themselves as the stronger pair of performances ("You are protected by the enormity of your stupidity!") but even then their ultimate fate earns neither satisfaction nor sadness, because I simply do not know or care about them enough to justify it.

Two shots of this film will sit with me for a long time, though:

1. the introduction of Cary Grant's character, in which he is filmed bravely and eerily from behind, showing only a silhouette of the man and his dark haircut.
2. the scene in which Rains famously tells his mother that he has made a big mistake, and her long, slow procurement of a cigarette in response.

1. Decisions are any non-trivial choice made for a specific reason.
2. The context behind a decision is very hard to retrieve after the fact and grows in difficulty over time.
3. The ability to revisit this context and update, invalidate, or buttress it is extremely useful in a variety of reasons.

Our decisions range from the monumental-yet-concise:

---
id: "0002"
title: What domain should we use now that we have buttondown.com?
date: 2024-05-14
status: implemented
---

We should shift to buttondown.com, but the process of doing so is very unclear and we need to take it slowly + carefully.

to the trivial-but-nuanced:

---
id: "0196"
title: "Unship django-simple-history"
author: Justin Duke
date: 2026-06-24
status: implemented
---

## Context

We carried `django-simple-history` for years to track changes to two objects: the
`Newsletter` and the `Email`. It installed mirror `Historical*` tables that copy
every field of the tracked model on every save.

It is the same kind of dependency we have spent the past year unshipping
(0148 django-safedelete, 0149
django-structlog, 0152 django-anymail): a general-purpose,
illegible, low-performance package doing work that our actual use case — narrow
and minor — does not justify. We already had a `*StatusTransition` model and
several other purpose-built ways to record the changes we cared about, so most of
what `django-simple-history` did was redundant. We held onto it mostly out of
deference to history, not because we were using it.

I have spent this month deep in the email lifecycle and now have both the
confidence that we should remove it and the loaded context to do so quickly
without coming back up to speed later. The removal is not urgent on its own — it
mainly cleans up the render and save/performance path — but the marginal cost of
doing it now, while the context is hot, is low.

## Decision

Remove `django-simple-history` and replace its two real use cases with
purpose-built models:

- Email body revisions → the home-grown `EmailHistory` model
  (`emails/models/email_history/`), one row per body change rather than a full
  per-field mirror on every save (#9795).
- Newsletter design changes → `NewsletterDesignHistory`.

We removed the package's models from Django's state but **deliberately retained
the underlying tables and their data** — `emails_historicalaccount`,
`emails_historicalemail`, and `emails_historicalnewsletter` — in case we ever
need to read the old revisions. (#9906 then dropped the orphaned `auth_user`
foreign keys those tables still carried, which were tripping a
`ForeignKeyViolation` on user deletion — BUG-387.)

## Consequences

- The save path no longer writes a full-object history row on every `Email`/
  `Newsletter` save; history is now scoped to exactly the fields we surface
  (email body, newsletter design).
- Three orphaned `Historical*` tables now live on production with no Django model
  in front of them. Like our other retired historical datasets (API requests,
  raw email events), the right end state is to archive them to ClickHouse and
  drop them from Postgres rather than leave them sitting in the primary database.
  That cleanup is tracked as a follow-up and is not blocking.

It is objectively not a free lunch in that it does take time for you to sit down and explain concisely in prose why you are doing a thing and what the other options are. It was most of all the null hypothesis of simply not acting. But a cost which serves as a forcing function to write, I mostly think of as a reward at this point.

The world is complex: with every patch of fog that lifts, I find four more in the distance. 1Only very recently have I started to understand knowledge as a perception of fog rather than a dispelling of it. And so I am very careful not to prescribe these days, unless I am so overwhelmingly confident in the universality of a given prescription. This is one such thing: keep a decision log.

(See also Oxide's public RFD system.)

Part of this was due to significantly downshifting my caffeine consumption (makes for a boring story, I know, but it was time to go from a baseline of four cups a day to two); the other reason is having spent most of my brain on things that are hard to write about and hard to spin back up on once I've distracted myself: Firewall/KYC concerns, systemic onboarding, and so on.

It was a good and quiet month. We started harvesting the tomatoes, and this weekend I made salsa from three pounds of delicious Roma. I started waking up even earlier to lift, before the sun (or, bless her heart, Lucy) have a chance to intrude. Lucy, who by the way now speaks in two-syllable bursts, who now makes a game out of grabbing my shoes when I say it's time to go to the store, who knows not just how to dance, but what I mean when I say dance.

Post
Self-hosting our CI, three months later
Back to Overcast
Victory is a lossy compressor
Indeterminate / Squash
Denormalization 101

I was young. I wanted something very badly and I was afraid that if I took my eye off it, I wouldn’t have it. And I was right. There was no other way to do it. And it meant choosing it over you. But it was always meant to be temporary.Just until I got what I wanted...But then I had to keep it.

I am reminded of the other recent George Clooney vehicle, Wolfs: this is self-indulgent in one dimension, and its merits are almost entirely carried by the efforts of Sandler and Clooney, both of whom give very strong performances which rescue the film from being Bad but do not carry it to greatness.

I also found myself wondering what Baumbach is up to right now. The script and direction here seem entirely thoughtless — not so bad as to be offensive, but neither interesting nor characteristic of his earlier and better work. I can dismiss things like the scattershot tone or the half-hearted performances from Laura Dern et al. as being intentional -- it is an ethereal, dreamlike film.

But the movie fails to do what I think it needed to do, which is to make us feel bad -- or novel in some kind of way -- for either character, even if for an instant.

Clooney plays a very light pastiche of himself: if you interpret the film as a story about Clooney himself, you are forgiven for doing so because he so comfortably eases into that role of charm and conviviality. He is a man who made it big, and in so doing had two lovely daughters who care little for him due to his absence -- an absence that he chose, time and time again, until there was no other choice to make.

(And much of the same criticism -- if it can be called that -- can be levelled at Sandler's character, who is a very realistic depiction of a guy worth millions of dollars whose biggest problem is that nobody will say "I love you" to him.)

I watched Somewhere earlier this year, and I think many parallels (Hollywood people and their Hollywood problems!) can be drawn between the two films, but the success of Somewhere is in what I called "the wattage and nuance of Dorff and Elle Fanning's performances"; both together and in isolation the two performances there stirred something beyond artifice in me in a way that Jay Kelly did not.

Lastly, the ending.

I really think the story of this film is that Baumbach — and Emily Mortimer, as co-writer — came up with the final scene and the final line, and then worked their way backwards from it into a movie. And to a small extent, that worked: the final scene, and the final line, cliche as it is, smashes me to bits. But it feels cut from a different movie -- a different life! -- than the one I spent two hours watching.

The well-behaved schema

Imagine the data behind an art gallery. Galleries run calls — open invitations for submissions — and artists submit entries. The application that captures all this stores it the way Codd would want: tidy, normalized, every fact in exactly one place.

Here's what a handful of rows actually look like — the keys (gallery_id, call_id, artist_id) are the threads you pull to stitch it back together:

Every fact lives once. An artist's state is on the artist; a call's deadline is on the call. This is normalization, and for the system that has to keep the data correct — accept a submission, change an address, never contradict itself — it is exactly right.

I honestly struggle to talk about normalization, and I think even the concept of database design (or at least data modeling) has become a little less in vogue because best practice has just sort of been absorbed into the collective subconscious. Everyone knows how to model stuff a little bit better now than they did 20 years ago. Most databases look something like the above.

Asking questions

Sooner or later someone asks an actual question. Say whoever's running the gallery wants to know how much of their interest is local — concretely: how many entries come from an artist based in the same state as the gallery running the call?

That's one sentence. Against the normalized schema, it's four tables and three joins, because the two facts you need to compare — the artist's state and the gallery's state — live at opposite ends of the graph:

select count(*)
from entry e
join call    c on c.id = e.call_id
join gallery g on g.id = c.gallery_id
join artist  a on a.id = e.artist_id
where a.state = g.state;

You have to hold the whole shape in your head — entry to call to gallery on one side, entry to artist on the other — just to line up two state columns. And this is the toy version — real questions pile on: break it down by gallery, restrict to this year's calls, weight it by how many entries each artist submitted.

This, at least in an abstract sense, has two problems:

1. Meaningful insights come from combining disparate datasets, and normalization makes that definitionally more cumbersome.
2. Joins are slow.

Simply eat the other tables

The answer is denormalization!

You build the thing that makes it easy:

This is denormalization, and the warehouse crowd has a dozen names for the result — a wide table, a one-big-table model, the flat fact table at the center of a star schema, a feature table if you're about to train something on it. ETL, materialized views, whatever — the implementation is a detail; the point is that this pattern has a dozen names.

The artist's state and the gallery's state now sit in the same row. You've reintroduced, deliberately, the redundancy normalization warned you about — Spring Open and Pace repeat once per entry — because the join you used to pay on every query, you now pay once.

And the query becomes the question, almost verbatim:

select count(*)
from entry_view
where artist_state = gallery_state;

How lovely!

[points at butterfly] is this a cache?

So obviously there's a reason we don't do this for everything: we now have to figure out how to build the table. This is a rich subject for which I am much less qualified or interested to opine; if you're reading this blog for answers, the answer is something like "run a daily cron which makes the big ol' join manually and reconstitutes the table".

At this point, you have yourselves a cached table with twenty four hours of freshness. You have traded (presumably) a bit of operational toil for a bit of... something. What is that something?

• Sometimes you're caching knowledge — you just want one clear, blessed definition of what an EntryView is, a shape everyone can point at and treat as the source of truth. If so, just through it in a view! Don't worry about materialization.
• Other times you're caching reads — the join itself is the problem, too slow or too expensive to pay for on every query. That's the one that earns a materialized table and an ETL pipeline to keep it fresh, operational toil and all.

Both are valid reasons, but as someone in the business of reducing his exposure to moving parts I am morally obligated to make sure you know which camp you're in.

Postscript: I once again recommend a data greenhouse

I wrote about building a data greenhouse four months ago, and it's largely in service of this problem. Being able to trivially answer stuff like "how quickly do we solve bugs from US-based users vs. EU ones?" is wildly actionable.

I envy you. You have your whole life ahead of you and you know exactly what you want to do. But forget the rat puke; write something beautiful.

You don't know zip! You think I'm going to end up selling appliances like my father? Chasing women around the store. I've got to give it a shot. Why are you trying to kill the two things that mean the most to me? Until yesterday you loved me and you loved us.

I watched this absolutely bizarre film solely on the back of being fascinated that Coppola had to do so much commercial work to support all of his less-than-successful creative work. It is an 80s film about going back to the future — which is to say, it came out one year after that film, and apparently this recontextualizes much of it. But as someone who really doesn't care that much about Back to the Future, I can take it on its own merits.

Its own merits are just: deeply strange?

You have Kathleen Turner being entertaining but entirely overacting the entire film, traveling back to her high school years with Nicolas Cage (whose best friend — by the way — is Jim Carrey) cosplaying as a 50s lounge lizard with the worst nasally accent you have ever heard. 1It has apparently taken me this long to discover that Cage was Coppola's nephew, a fact made even funnier by his having also cast Sofia in a minor speaking role.

You almost certainly know exactly how this movie is going to turn out by the 15th minute or so, and the question then becomes whether the scenery along the way makes it worth your while. Bizarre choices abound in every line reading and abrupt scene transition: almost gratuitous sacrifices to requisite 80s comedy — the snarky high schooler who gets her comeuppance, and so on, punctuated by moments of melancholy and tenderness that make you forget just what it is you're watching. You have a faux beatnik deploying Yeats in a way that works both textually (it's a very lovely, sonorous poem) and metatextually (the authors understand that the pilgrim soul is Yeats' way of being a dick).

Cage's character is in many ways the protagonist of the film, and Turner the viewpoint character; she remains static while our understanding of him changes radically. Charlie is vain, ridiculous, overbearing, hyperreactive; he also seems to genuinely love the protagonist. His dreams get dashed not due to cosmic justic nor awful luck but due to the ways of the world; he errs, and he attempts to atone for his errors. The clever trick of the film is that Turner does not end up leaving the past with a better understanding of herself so much as she leaves with a better understanding of her soon-to-be ex-husband: that he is a man who wanted big things that did not quite materialize; that he is a buffoon who will do anything for her.

For the first two-thirds, the film is dominated by the schizophrenia of jumping between the two movies it's trying to be: the reflective, somber, Proustian meditation and the formulaic nostalgia-driven cash-in. This incoherence finally reconciles in the movie's sweetest scene (in a movie already filled with them), in which Turner visits her grandparents, a scene which fulfills two purposes:

1. Her grandmother is psychic and her grandfather belongs to a Masonic lodge that is actually a time cult
2. Her character is the person who more than anything else that could be granted by a trip to the past — fortune, fame, power — chooses an evening with her grandparents

The film is both fatalistic and deeply, deeply humane; it is a lucid dream, in which you know (however hazily and briefly) that you will wake up in your own bed, but are willing to get taken along for the ride in hopes of remembering something interesting.

One example comes to mind from this weekend, when I was trellising a handful of truly overgrown cherry tomato plants. Cherry tomatoes are indeterminate, which means there's no size at which they stop growing and start to ripen. They're like mint, secretly — they will happily grow and grow and grow forever. The only thing stopping them, barring human intervention, is the comic rapidity with which they'll die: from blight, from dehydration, from sheer overextension — almost as quickly as they prospered, if not more so.

There are a lot of ways to curtail this, and one of the things we do is trellis. We've got this very fun, K'nex-esque trellis system that acts as a kind of three-dimensional grid. The tricky bit is that you can't really set it up before you've set up the tomato; you build the trellis around the plant, carefully, using it as an opportunity to find which branches are in danger of touching the ground. It's a satisfying exercise in its own right. Often, when Haley and I tear down the tomato crop for the year, we'll sit for a minute and just look at our lovely little cityscape of green rods and connectors before we tear those down too and throw them in the bucket. Because as cool as they look, there's no real reason to keep them around in an empty bed.

And of course structure is necessary but insufficient. So we did the things one does when tomatoes are overgrown. First, Lucy and I started with the two existential threats. Anything in danger of stooping down to touch the bare ground had to be either scaffolded immediately or mercifully pruned. Then came the work of trying to establish a sight line to the soil, which is a useful proxy for two things: airflow and sunlight. The plants had a couple of little yellow bits here and there, but no blight — nothing too serious.

From there we moved on to the more qualitative work, and in doing so started to discover just how bountiful these couple of plants had been. I tried not to wince at every little tug Lucy gave at the root. Slowly and surely, the plants started to look less grisly, less insanely overgrown, until the garden resembled a garden and not a jungle — something I could show my mother-in-law with pride and not fear.

And finally, at the end of this week-long journey — every morning Lucy waking up with me, having a few eggs, and going outside before the humidity made the prospect unbearable — we discovered the very back of the garden, hidden and prospering all this time: a terrific squash plant, happy and beaming, its first fruit ready not to be plucked or picked but cut with one ginger motion.

For the past three days, Lucy has refused to eat anything until she gets to go look at her squash. I do not like squash, and yet it appears it has now earned a permanent place in our harvest.

One of the joys of my recent cinema excursions has been getting to understand some of these mechanics — even when the films themselves aren't particularly successful. There's Vanya on 42nd Street, a film whose lack of production is literally part of the text, and which uses that fact to brilliant effect. And there's Mindwalk, a film forgotten to history, with interesting elements of its zeitgeist, that nonetheless conjures a dreamlike quality out of the graininess of its direction layered over the beauty of its landscapes.

Somewhere in the middle of these sits The Man from Earth, which is probably best introduced through the lens of its screenwriter, Jerome Bixby — a quasi-famous science-fiction writer who did a lot of work on The Twilight Zone (as one might guess from the title) and the then-successful B-movie side of Hollywood; the film's executive producer is his son, and it is hard not to think of this as more of an act of Asthi Visarjan than of genuine creative commitment.

This is very much a five-act play captured on camera rather than a work built for the medium. The entire action takes place in a single remote house, and unlike the aforementioned Vanya it is filled with actors you've never heard of performing, by and large, very poorly. The music is bad; the lighting is bad. 1

And yet, for a certain type of person — i.e. myself, and perhaps you as well — this will be a movie you cannot tear yourself away from, even as it grows more and more absurd. The conceit of the exercise is very simple: the central character reveals himself to be a man who is (for the sake of this essay) immortal, then he invites his colleagues — a coterie of university professors in various disciplines — to interrogate him and to challenge the veracity of his claim.

That is the film, by and large: professors quizzing an immortal man on what he should or should not know and what he should or should not remember. If you think that is interesting, it may be worth watching; if you don't, turn away.

As poor as every other part of the product is, the writing (not unlike the best of Bixby's Twilight Zone episodes) is arresting not for its clarity or beauty but because it forces you, however briefly, to completely eject yourself from your frame of reference. It's a really, really fun premise, delivered earnestly and intelligently.

What is the difference between someone with a sufficiently encyclopedic memory and understanding of the world and someone who has actually lived it? You might think understand that this is suddenly a more relevant question than it has been.

The NBA's conference finals wrapped up this past week, and as a Heat fan and a Seattle émigré I was pleased with both results. Happy that the Cavs lost, because I still resent them for being the destination to which LeBron fled in 2014; happy that the Thunder lost, because fuck Howard Schultz. 1For the uninitiated: Schultz, as owner, presided over the sale of the Seattle SuperSonics in 2006, which led directly to their relocation to Oklahoma City. The Thunder are, in a very real sense, the Sonics. I am not over it.

Both losses were noteworthy.

The Cavs were, after game three, safely assumed to be dead in the water — no NBA team has ever come back from a 3-0 deficit in the playoffs. Their head coach, JB Bickerstaff, infamously (yes, it can already be classified as infamous) claimed that from an analytics standpoint they were really up — that the underlying numbers had the series at a 2-2 coin flip they happened to be losing.

The Thunder, last season's champions, were being discussed around the halfway mark as candidates for the greatest team of all time: whether they could break the all-time regular-season wins record, or, more humbly, be the team that finally snapped the league's eight-season no-repeat-champion streak. Those discussions promptly ended in December, when — in what turned out to be foreshadowing — the Spurs beat them three times in ten days. Even gods can bleed. Now the conversation has gone the other direction entirely: whether they should blow up their core three and pursue a win-now trade for Giannis, or some similarly older-but-better superstar.

All of this is, in my opinion, kind of silly, by all parties involved.

Bickerstaff should not have tried to invoke the spirit of Pythagorean victories to motivate his team or deflect criticism about their dire straits. And yet — it's not like he was completely incorrect. In much the same way that, if you know with absolute certainty a coin is rigged to land heads 70% of the time, you shouldn't start betting tails just because tails came up the last three times. 2Now, if it comes up tails ten times in a row, maybe that's a sign to reevaluate your threshold for "absolute certainty."

And the discourse around the Thunder's prospects glosses over the fact that the second-best player on their team — and, during some stretches, arguably the fourth-best player on their team — were both out for the entire series. Which is a boring but plausible explanation for why they lost. (It should be noted that they lost in seven, and scored more total points than the Spurs across the span.) But the narrative of Wemby, the seven-foot-seven godkiller, has taken root.

Let me be clear: the Knicks and the Spurs did win, and no number of hypothetical simulations changes or devalues that fact. But as soon as we turn the page onto next season, the nuances that led up to the result will grow hazier and dimmer and more nebulous, until recovering them requires archaeology rather than recall.

The NBA is a league where we talk about rings, not net rating.

Which is to say: victory, whether over the course of a single game or an entire season, is not a lagging metric assembled from the true granules of play-by-play data. It is the thing itself — the reified artifact. The banner, the line in the record book, the ring.

And there is nothing wrong with this, in the same way that it is no crime that both PNGs and JPEGs exist. Victory is a lossy compressor: it takes the full, lossless record of a season and squeezes it down into something small and portable, discarding almost all of the granular detail in order to do so. It is enormously useful to be able to optimize for file size — for what travels, for what gets remembered. But it is not the only use.

All of this is to say: I bring it up not just because I'm waiting for Zach Lowe to publish his Tuesday episode previewing the Knicks-Spurs series, but because in America sports are metonymous with many things, and one of those things is business.

And I have found it far more revealing, in trying to understand a company that has — capital M, capital I — Made It, not to read their most recent batch of press releases, but to crank up the Wayback Machine and go look at the launches they shipped in 2018 that failed.

The press release is the JPEG. The failures are the bits that got thrown away. If you want to understand how something actually won, you don't get to recall it — you have to decompress it, and the only way to recover what victory discarded is to dig.

None of my gripes with Overcast have been fixed, or even assuaged. But paper cuts are less annoying than other forms of pain. If I really wanted to, I could sit down for thirty minutes and assemble a meaningful list of everything that bothers me about the first-party app — but instead I'll present only the two that are actually load-bearing.

The first, and the trivial one: there is no easy way to search for episodes within a given podcast feed. I'm not talking about clever, fancy, transcription-based search — just searching by title. Apple Podcasts' search functionality has many oddities, but this one is bizarre, and it is crucial for me whenever I'm trying to dredge up an old episode. This probably reveals something idiosyncratic about my listening habits: there are very few podcasts I subscribe to — exactly one of them technical — that aren't evergreen.

The second point is less about features and more about existential positioning. Compare the home screen for Apple Podcasts to the home screen for Overcast. One of these apps is designed with the primary goal of letting me listen to the podcasts to which I've subscribed. The other is designed with the primary goal of getting me to listen to a podcast to which I have not.

I could make grand sweeping gestures about how this reflects various pricing models and success criteria — and maybe I'll do that in some future essay — but I actually don't care about the bigger picture. My point is narrower: Apple Podcasts pursues goals that result in a worse experience for me.

And so I'm not back on Overcast out of any solidarity for a fellow independent developer, nor because of some vague, abstract sense of it being capital-B Better. I'm back on Overcast because I like it.

1. The first is the fungibility of fatigue. Also known as the spoon theory,1To be clear, my point is with the colloquial extension of spoon theory to able-bodied people like myself, and not the chronic illness context in which it was coined. it is roughly the notion that everything we do — from the mundane (brushing one's teeth, taking a shower) to the expensive (entering flow state for four hours of incident response) — carries some vaguely quantitative measure of toil, all of it drawn from a single reservoir over the course of the day. Like a wizard spending mana to cast spells at varying levels. This model, like all models, is useful insofar as it offers some bit of truth: for everyone there is an innate drain from everything we do, even the things we don't think of as draining, and both those numbers and the size of the central reservoir vary from person to person.

2. The second is the idea that productive work is inherently toilsome in a way that consumptive work is not — a concept often espoused by Cal Newport, for example, generally as a kind of groundwork lemma, to then advocate against consumption in favor of productive work as a form of leisure. This, too, contains some scintilla of truth: on net, work that we would describe as productive does have characteristics distinct from work that we would describe as consumptive. But the dichotomy is fake, and with enough rigor can be made contradictory. I take quite a bit of pride in my approach to consumption; when I am watching a movie or reading a book it is the only thing receiving my attention, and I am often thinking very, very hard as I do so. And conversely, many bits of ostensibly productive work are without a doubt the easiest and most energizing parts of my day — fixing a quick bug, or cooking Lucy an omelette.

The synthesis of these two anti-revelations is probably obvious, and perhaps one that you arrived at years before I did: energy is not a trivial thing, whether in the growing or in the reaping.

May was filled with days in which I would happily and ably spend sixteen hours straight playing with Lucy and cleaning the house, then running a dozen errands, then reviewing a handful of PRs. And then suddenly it is 9pm, and for all the Café Bustelo in the world I cannot summon the energy to open Slack for the first time in twelve hours — not out of fear or dread of what may await me, but because in that moment a dozen hashtagged channels lit up and awaiting my attention feels akin to a text from my friend Colin asking whether I'd like to go on a quick eighteen-mile jog to shake the rust off.

It took time to earn the comfort of hitting CMD+Q on Slack. Two years ago, as I have written, a couple of days away from the business meant a week of lost growth, meant a week of angry customers. Now: I spent a week away and came back to one of my lovely support folks genially informing me that everything had gone great, and that I should take more time logged off. 2This conversation concluded with her daring me to stay logged out of her customer support tool forever — a dare which I happily accepted. Thanks, Anita.

How do you relax when the things that once brought you energy now demand it? One way involves a very happy dog with a newly-repaired ACL and what is frankly the most disgusting tennis ball I have ever seen or felt, its entire surface smothered in a slime-like residue of slobber and dirt from the herb garden, followed by a night in which I go to bed at 9pm, arms sore and grateful, brain too empty to entertain any thought of the days ahead.

I hope you had a lovely May. Mine was filled with rest and unanswered push notifications, and now it is time to spend a little bit of the former on a little bit of the latter.

Post
On self-updating screenshots
LLMs and Buttondown
Just aim the cannon correctly
Buttondown no longer runs Redis
Screen record more
Be careful what you make easier
What matters
ccusage