• The REPL: Issue 146 - October 2026

    AI Promised Less Work. I Have Never Worked More

    Orestis Ioannou points out that he doesn’t have less work in the age of AI. Neither do I. The work is different, but I’m not sitting around drinking coffee. I never took the promise of less work seriously anyway. If anything, what I can do by myself has expanded.

    Living in the Weimar era of Ruby

    The title is clickbait, and the article is not what you imagine. I’m linking to it because it points to this exchange, which I found insightful.

    Nate Berkopec:

    I just think you need to have some epistemic humility Most important development in computing in 20 years comes along, and the exact stack you’ve been working on that whole time happens to be the perfect stack for the next 20 years? OK.

    José Valim:

    You are right but it also feels short-sighted? You have the most powerful tool you ever had, you have become a 1000x maker, and you can’t think of how to make your stack 10x better?

    Yes, Rust is fast, the type system catches bugs, but there is so much beyond it.

    • Why not make Ruby 10x faster?
    • Why not make Ruby (and therefore Rails) really great at concurrency?
    • Why not add a banging type system to Ruby that can provide guarantees beyond Rust?
    • Why not embed SQLite3 into Rails with a replication protocol so you can really compress the stack beyond a single server?
    • How to preemptively fix most bugs from the most critical parts of Rails, such as database pools?

    Yes, who cares about ActiveSearch, but there are so many ways we can fundamentally improve our stacks that go beyond asking the agent to just crap out code. Phoenix is still the only framework that ships with presence, because it turns out it is deceptively a hard problem to solve correctly, but somehow all issues are solved?

    I understand some folks have no interest in doing any of the above, and that’s fine, but then at least pass the baton to the people who want to do exactly that.

    PS: I say all of this with love ❤️

    Read on →

  • The REPL: Issue 145 - September 2026

    Kafgres: Embedding a Kafka Broker into Postgres

    Interesting project: a Kafka broker built into Postgres as an extension. I’ve considered Kafka for several projects, but I’ve yet to use it.

    It’s Time to Investigate the AI Labs

    Cal Newport is wondering the same thing I am:

    Why not pursue criminal liability for them running systems they knew would likely commit crimes?

    There are already laws on the books against unauthorized access to computer systems. I haven’t heard of any authorities investigating the AI labs for the hacks they’ve already made public. Why not? The labs directed their computers to do something on their behalf, and that something is a crime. Investigation seems like the logical next step. Did rubygems.org call the authorities after discovering their infrastructure was being abused? Their update doesn’t say.

    Read on →

  • The REPL: Issue 144 - August 2026

    Today’s REPL is different from most. I usually point to a few interesting articles. This time I found myself writing at length about a single one.

    Accepting a messy git history

    Andreas Zwinkau describes two kinds of git users: commit often, or rebase carefully. I don’t see it as a choice between the two. It’s more nuanced.

    I do both. While developing, I commit whenever I reach a meaningful amount of work 1. Sometimes that’s failing tests that expose a bug, so the red-green cycle lives in the history. Sometimes it’s a class or module the feature needs but that isn’t hooked up to the rest of the system yet. It’s a thoughtful process, but it doesn’t always leave a pristine history.

    Before I open a pull request, I go through that history. Sometimes I took a path and later backtracked. A file might exist only in this branch because I decided the naming needed work. None of that helps anyone later, so I rebase and squash to present a better story in the pull request.

    Once I open a pull request, I don’t rebase, squash, or otherwise change the history. Not even squash merges. Once reviewers have commented, rewriting history creates more work for them. GitHub presents a “changes since your last review” button, which is extremely useful. A force-pushed rebase or squash destroys it, and the reviewer has to read the whole PR again. I care more about reducing friction with my teammates than about a pristine git history.

    Is a pristine git history even worcth having?. Most arguments I’ve come across say a good history gives historical context about a code base. I agree, to a point. Commit messages that all say “fix code” help no one. But a squash-merged history loses the changes reviewers asked for. They live in the pull request, not in git. So does a history rewritten to look like the code arrived fully formed. I prefer the actual history to an abridged version.

    As for stacked pull requests, I think a lot of folks miss the point. They can split a large change into smaller chunks for review, but in practice I use multiple PRs when I need to sequence deployments. For example, a PR that prepares the code for a column deletion, then a stacked PR with the migration that deletes it. Sometimes a conceptual unit of work has to ship in multiple PRs. That’s different from a commit history that tells a story but can be deployed all at once. As for the “read the commits individually” argument: I’ve never been on a team that does that. Maybe because GitHub doesn’t encourage it, but whatever the reason, I don’t see it as a practical way to review PRs.

    1. This has changed somewhat with the use of agents. ↩

    Read on →

  • The Backlog Is Infinite

    A friend asked me if my company is going to fire half of my team. He doesn’t write software. A few weeks earlier he had installed Claude Code, described an app he wanted, and got one. More or less. If he can do that knowing no programming at all, what does a company need a whole team of engineers for?

    I get some version of this question regularly now, almost always from friends outside of software. I’m not worried. But not for the reason they expect.

    Read on →

  • The REPL: Issue 143 - July 2026

    The Short Leash AI Coding Method For Beating Fable

    The author describes staying in the loop as the AI writes code, steering constantly. One thing I’d add to their toolkit: ask the AI to produce diagrams. ERDs, state diagrams, sequence diagrams – whatever the task calls for. Just by drawing them, it often finds bugs in the design, before I even review them.

    DON’T YOU MEAN EXTINCT?

    If we are at the cusp of a paradigm change, it makes sense that we need to evolve. To adapt. Just like the stop-motion animators did. It turns out they had more to offer than stop-motion know-how. They also knew a great deal about dynamics, and about what movement looks natural.

    Should You Use AI for a Task? Here’s a Simple Way to Decide

    Really useful heuristic: Is it work or the gym?

    An example that comes to mind: I can ask AI to summarize the instruction manual for my Instant Pot. The manual was badly written in the first place, and all I need to know is which button to press. But asking AI to compress a novel into a paragraph? What’s the point? The enjoyment of a book is reading it, learning what happens at the book’s own pace.

    Read on →