← @bgSponge

Pencils Down, Notation Up

Summary

Sam Ruby answers DHH's Rails World 2026 pencils-down keynote by arguing agents still need compact notation at the top of the drill.

  1. Keep notation at the top of the drill.

    Agents can target Rust, C, or microcode, but the editable source of truth should stay compact and intentional.

    Nobody would choose to maintain the C. That's what makes it a compilation target.

    Let the drill go as deep as it can. Just keep the notation at the top.

  2. Campfire in Rails beats Campfire in C for agents.

    The Rails app is about 60k tokens and fits in context; the compiled C is about 4M tokens and about 70× too large.

    The Rails app fits in context whole; the C is only ever seen in slices.

  3. Source of truth needs five properties.

    It must fit in context, say each thing once, keep intent, produce the same result every time, and preferably look like training data.

  4. A precise prompt is already a program.

    Pinning every association, validation, callback, and route recreates a web-app DSL that Rails already is.

    Regenerate from the same prompt twice and you get two different programs, each of which has to be verified again.

  5. Compile-time meaning recovers most of the speed.

    Emitting Campfire as a native binary yields 7–8× throughput and 92% less memory versus its Dockerfile deploy, and most of Rails' cost was runtime interpretation of declarations.

Read the original ↗Save to your Sponge

Summarized with Sponge. Quotes are the author’s own words.

More from @bg

All readings →