← Rust in PeaceIntroChapter 1 of 7 · Section 8 of 59Sections1. Intro1. May my soul rust in peace2. 5 Years at the Fruit3. 4 years finance data & platform engineering4. 1 year teaching programming5. What I realized is6. Decided to be a lawyer in New York7. What our firm does8. NeonLawNavigator9. Agenda10. Las Vegas, 2011 — where I learned to program2. The Rails Lesson11. Convention over configuration12. The database was a shared design13. Controllers — where a request becomes a decision14. Parameter handling — the shape of what comes in15. Middleware — the layer I didn't know I needed16. "It works on my machine"17. How new all of this still was18. From Rails conventions to Navigator19. A eulogy for my programming career3. Shared craft compounds20. Keep domain seams in Rust, where interest compounds21. Widely available — governed in the open22. A cautionary tale — Java, Oracle, and the price of a single owner23. Say it with your whole chest4. Six ways to know a change holds24. One giant change deserves more than one glance25. The compiler asks whether the program can be true26. Clippy and rustfmt ask whether the code speaks our dialect27. Tests ask whether the promise still holds at the boundary28. Bloom turns verification into a learning loop29. Marketing copy must explain the way, not only the claim30. Three workshops, three people, one method31. Fast generation, slow enough verification5. From Law to Workflow32. The goal — deterministic workflows from law33. Step 1 — read the law34. Step 2 — write the behavior before the code35. "It works on my machine" — so we stopped trusting my machine36. Step 3 — the template: a questionnaire and a workflow37. Step 4 — the attorney gate is a graph invariant38. Step 5 — signature is a modular step39. Step 6 — the filing, run durably40. "It works on my machine" — even when my machine dies41. Why a workflow beats a prompt42. Privacy-preserving operations are part of the product6. Rust All the Way Down43. We did not start all Rust44. From Postgres to Rust — over a bridge, since dismantled45. The runtime story: keep the seam, change the engine46. One deployment bucket; many matter repositories47. Rust where we can own the path; partners at the edge48. Rust reaches the places lawyers work49. I want a commercial relationship with everything I depend on50. Always the latest, always Rust51. Swap the seam — it still works52. The crates we actually run on53. Ethics is part of the stack54. The simplest developer environment I can get away with55. The online developer environment56. "It works on my machine in the cloud — and on yours, and on my client's"57. Where we are today — live by August 2058. Betting on ourselves — Rust in peace7. Wrap Up59. Take the method homeNeonLawNavigatorgithub.com/neon-law-foundation/navigatorView all slidesOpen display← PreviousNext →