Neon Law
  • Notations
  • Nimbus
  • Workshops
  • Show-and-tell
  • Sign in

Rust in Peace

A Neon Law Foundation talk for Rust NYC on how we use Rust to improve access to justice: deterministic workflows from law — statute to Cucumber feature to template to notation — dissected one modular, attorney-gated step at a time, with every code slide an exact copy of the shipped repository kept honest by a grounding test.

A Polin Shook talk for Rust NYC.

Rust in Peace is a eulogy to my programming career. Over the past year, teaching coding at Apple, I realized nearly all my students were vibe coding and had stopped needing me. That was the signal to go back to practicing law.

Our firm runs its entire practice on one Rust monorepo: the store, the durable workflow engine, identity, telemetry, PDF generation, and the browser surface. We are currently litigating nine-figure matters, and the software is what gives us the context to win them. This talk walks through what that actually looks like in production, including our migration from Postgres to SurrealDB. That move came from discovering that the hardest question in legal work is a graph one, because we deal with people, their relationships, and their problems.

You will see how it fits together, and how we choose Rust vendors all the way down: Restate, Rauthy, OpenObserve, Pingora, Stalwart, and Regorus. Writing software is not my job anymore. That is only possible because the ecosystem is this good, because the LLMs are this good, and because communities like RustNYC are this good. Please come to my retirement party and let us get crabby together.

Start →View all slidesView as Markdown
1

Chapter 1

Intro

  1. 1Agenda
  2. 2Las Vegas, 2011 — where I learned to program
2

Chapter 2

The Rails Lesson

  1. 3Convention over configuration
  2. 4The database was a shared design
  3. 5Controllers — where a request becomes a decision
  4. 6Parameter handling — the shape of what comes in
  5. 7Middleware — the layer I didn't know I needed
  6. 8"It works on my machine"
  7. 9How new all of this still was
  8. 10From Rails conventions to Navigator
  9. 11A eulogy for my programming career
3

Chapter 3

Shared craft compounds

  1. 12Keep domain seams in Rust, where interest compounds
  2. 13Widely available — governed in the open
  3. 14A cautionary tale — Java, Oracle, and the price of a single owner
  4. 15Say it with your whole chest
4

Chapter 4

Six ways to know a change holds

  1. 16One giant change deserves more than one glance
  2. 17The compiler asks whether the program can be true
  3. 18Clippy and rustfmt ask whether the code speaks our dialect
  4. 19Tests ask whether the promise still holds at the boundary
  5. 20Bloom turns verification into a learning loop
  6. 21Marketing copy must explain the way, not only the claim
  7. 22Three workshops, three people, one method
  8. 23Fast generation, slow enough verification
5

Chapter 5

From Law to Workflow

  1. 24The goal — deterministic workflows from law
  2. 25Step 1 — read the law
  3. 26Step 2 — write the behavior before the code
  4. 27"It works on my machine" — so we stopped trusting my machine
  5. 28Step 3 — the template: a questionnaire and a workflow
  6. 29Step 4 — the attorney gate is a graph invariant
  7. 30Step 5 — signature is a modular step
  8. 31Step 6 — the filing, run durably
  9. 32"It works on my machine" — even when my machine dies
  10. 33Why a workflow beats a prompt
  11. 34Privacy-preserving operations are part of the product
6

Chapter 6

Rust All the Way Down

  1. 35We did not start all Rust
  2. 36From Postgres to Rust — with a bridge
  3. 37The runtime story: keep the seam, change the engine
  4. 38One deployment bucket; many matter repositories
  5. 39Rust where we can own the path; partners at the edge
  6. 40Rust reaches the places lawyers work
  7. 41I want a commercial relationship with everything I depend on
  8. 42Always the latest, always Rust
  9. 43Swap the seam — it still works
  10. 44The crates we actually run on
  11. 45Ethics is part of the stack
  12. 46The simplest developer environment I can get away with
  13. 47The online developer environment
  14. 48"It works on my machine in the cloud — and on yours, and on my client's"
  15. 49Where we are today — live by August 19
  16. 50Betting on ourselves — Rust in peace
7

Chapter 7

Wrap Up

  1. 51Take the method home
Contact us — support@neonlaw.orgTransparency & public disclosures
  • Neon Law Foundation
    5150 Mae Anne Ave Ste 405-9999, Reno, NV 89523

Neon Law Foundation is a Nevada nonprofit corporation and a 501(c)(3) tax-exempt organization. It does not practice law and cannot represent you.

Nothing on this site is legal advice, and nothing here creates an attorney-client relationship.

© 2026 Polin Shook & Neon Law