Why does code still matter when LLMs can write it? Bryan Cantrill traces Rust’s infrastructure-first design to explain what we should preserve as software development changes.
Recorded at Rust NYC, this talk connects abstraction and accidental complexity with Rust’s ownership model, safety, and performance. Bryan explores compiler feedback, the crate ecosystem, the risk of generating unnecessary work, Gas Town as a cautionary tale, and using LLMs to deepen understanding. The full Q&A covers disciplined use, writing policy at Oxide, Clojure, software craftsmanship, and async cancellation safety.
For Rust developers, infrastructure engineers, and teams deciding how to use LLMs in software development.
Chapters
0:00 Introduction
1:11 Before Rust: developer ease and production costs
12:22 Abstraction and accidental complexity
18:02 Four kinds of software systems
25:22 The revolutionary language paradox
29:27 Rust as a tool for infrastructure
37:49 Rust’s bargain: ownership, safety, and performance
47:09 Into the LLM age
49:55 Why Rust appeals to LLMs
52:21 Vibe coding and understanding the code
55:56 The peril of LLMs: laziness lost
58:47 The management consultancy effect
1:04:09 Gas Town as a cautionary tale
1:06:03 Use LLMs to strengthen understanding
1:09:17 Learn Rust: code still matters
1:12:37 Further reading and listening
1:13:56 Q&A: additive use and discipline
1:16:51 Q&A: writing policy at Oxide
1:18:58 Q&A: Rich Hickey, Clojure, and infrastructure
1:20:42 Q&A: LLMs and smaller language communities
1:23:29 Q&A: protecting software craftsmanship
1:25:48 Q&A: async cancellation safety
1:28:41 Q&A: an internet-scale change
1:30:38 Q&A: build systems and RFD 576
Bryan Cantrill — Code Matters: Reflections on Rust in the LLM Age
Recorded at Rust NYC, Datadog, New York City, October 22, 2026.
Includes the talk and audience Q&A.
#RustLang #LLMs #SoftwareEngineering