Neon Law
  • Fractional CTO
  • Litigation
  • Fractional GC
  • Legal Services
  • Sign in
← Rust in Peace

Rust All the Way Down

Chapter 6 of 7 · Section 58 of 59

Sections

1. Intro

  • 1. May my soul rust in peace
  • 2. 5 Years at the Fruit
  • 3. 4 years finance data & platform engineering
  • 4. 1 year teaching programming
  • 5. What I realized is
  • 6. Decided to be a lawyer in New York
  • 7. What our firm does
  • 8. NeonLawNavigator
  • 9. Agenda
  • 10. Las Vegas, 2011 — where I learned to program

2. The Rails Lesson

  • 11. Convention over configuration
  • 12. The database was a shared design
  • 13. Controllers — where a request becomes a decision
  • 14. Parameter handling — the shape of what comes in
  • 15. Middleware — the layer I didn't know I needed
  • 16. "It works on my machine"
  • 17. How new all of this still was
  • 18. From Rails conventions to Navigator
  • 19. A eulogy for my programming career

3. Shared craft compounds

  • 20. Keep domain seams in Rust, where interest compounds
  • 21. Widely available — governed in the open
  • 22. A cautionary tale — Java, Oracle, and the price of a single owner
  • 23. Say it with your whole chest

4. Six ways to know a change holds

  • 24. One giant change deserves more than one glance
  • 25. The compiler asks whether the program can be true
  • 26. Clippy and rustfmt ask whether the code speaks our dialect
  • 27. Tests ask whether the promise still holds at the boundary
  • 28. Bloom turns verification into a learning loop
  • 29. Marketing copy must explain the way, not only the claim
  • 30. Three workshops, three people, one method
  • 31. Fast generation, slow enough verification

5. From Law to Workflow

  • 32. The goal — deterministic workflows from law
  • 33. Step 1 — read the law
  • 34. Step 2 — write the behavior before the code
  • 35. "It works on my machine" — so we stopped trusting my machine
  • 36. Step 3 — the template: a questionnaire and a workflow
  • 37. Step 4 — the attorney gate is a graph invariant
  • 38. Step 5 — signature is a modular step
  • 39. Step 6 — the filing, run durably
  • 40. "It works on my machine" — even when my machine dies
  • 41. Why a workflow beats a prompt
  • 42. Privacy-preserving operations are part of the product

6. Rust All the Way Down

  • 43. We did not start all Rust
  • 44. From Postgres to Rust — over a bridge, since dismantled
  • 45. The runtime story: keep the seam, change the engine
  • 46. One deployment bucket; many matter repositories
  • 47. Rust where we can own the path; partners at the edge
  • 48. Rust reaches the places lawyers work
  • 49. I want a commercial relationship with everything I depend on
  • 50. Always the latest, always Rust
  • 51. Swap the seam — it still works
  • 52. The crates we actually run on
  • 53. Ethics is part of the stack
  • 54. The simplest developer environment I can get away with
  • 55. The online developer environment
  • 56. "It works on my machine in the cloud — and on yours, and on my client's"
  • 57. Where we are today — live by August 20
  • 58. Betting on ourselves — Rust in peace

7. Wrap Up

  • 59. Take the method home

Betting on ourselves — Rust in peace

Choosing these vendors is betting on ourselves. If we write successful Rust, our vendors write successful Rust — a healthy ecosystem that stays usable for many years. That lets the firm focus on winning cases, and lets me Rust in peace: no longer a full-time developer, standing on the shoulders of giants.

Presenter notes

Here is the closing thought, and it is the whole talk in one move. Every vendor on that slide is a company that made the same bet we did: build the serious thing in Rust, stay current, publish the crate. So choosing them is not outsourcing — it is betting on ourselves twice. The same language, the same toolchain, the same crates.io; when we write successful Rust, the ecosystem that makes our vendors successful gets stronger, and when they succeed, the foundation under us gets firmer. That is what a healthy ecosystem is — not a moment of hype, but an environment that compounds and can be used for many years to come. And the payoff is the point of the whole firm: that stack runs so we can focus on winning cases. Early in this talk I gave a eulogy for my programming career. Here is where it rests: I no longer have to consider myself a full-time developer, because I am building on the shoulders of these giants — the foundation that governs the language, the maintainers who ship the crates, the vendors who run the clouds. The title was the plan all along. Rust in peace.

View all slidesOpen display
← PreviousNext →
Neon Law
BlogContactFoundationNavigatorPresentationsWorkshops
Contact us — contact@neonlaw.com+1 510 800 2080
  • Nevada
    5150 Mae Anne AveSte 405-9002Reno, NV 89523
  • New York
    12 E 49th St18th FloorNew York, NY 10017
  • Washington
    720 Seneca StSte 107-715Seattle, WA 98101

© 2026 Shook Law PLLC and Neon Law Foundation

This is attorney advertisement. Nothing on this site is legal advice. Neon Law is the trade name of Shook Law PLLC, and an attorney-client relationship begins only with a signed retainer between you and Shook Law PLLC. Published flat fees cover the scope each one names and do not include third-party filing fees. Every legal matter is different, and past results do not guarantee a similar result.

Shook Law PLLC is a proud supporter of the Neon Law Foundation , a 501(c)(3) nonprofit.

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.

5150 Mae Anne Ave Ste 405-9999, Reno, NV 89523
support@neonlaw.orgTransparency & public disclosures

Powered by Neon Law Navigator #26.8.20-hotfix.4

Open source — neon-law-foundation/navigator GitHub stars 2