Uploaded August 2026 | Updated November 2026, 3 days ago
At RustWeek 2026, the Rust Project Content Team talks with Jynn Nelson of Ferrous Systems about safety-qualifying the Rust compiler, a code coverage murder mystery, consensus building, and the Rust Project's emerging policy on LLM contributions.
Jynn shares how trying to fix a broken "go to latest version" button on docs.rs in 2019 turned into fixing the whole docs.rs build, joining the docs.rs team, and seven years in the Rust Project since. Topics include:
- What Ferrocene's safety qualification and certification work adds on top of Rust's built-in guarantees: external assessment by TÜV, line coverage across the certified core subset, and a semantic diff reviewed every release
- Why Ferrocene releases every three months instead of yearly: staying close to upstream Rust so users never have to choose between the qualified compiler and the latest features
- Qualifying a compiler without a standardized Rust language specification: writing your own specification and testing against it, which became the FLS, now maintained in the Rust Project
- The code coverage murder mystery behind Jynn's talk: three or four overlapping bugs bad enough to delay the first certified-core release, and fixing each layer so it can never happen again
- Consensus building and debugging as the same skill: breaking a hard problem down and asking "where would I start?", plus Jynn's six-hour "How to learn hard things" workshop
- The proposed rust-lang/rust LLM policy: allowing LLMs for debugging, review, and discovery; holding LLM-authored code to a higher standard than human code; and requiring your own words in PR descriptions and comments
- Why completing good first issues with an LLM defeats their purpose, and why people should put more back into the commons than they take out
Jynn's RustWeek 2026 talk, "Precise, consistent, and reliable code coverage": youtube.com/watch?v=P9lmSc4oLFs
Links and resources:
- Jynn's blog: https://jyn.dev/
- Jynn on GitHub: github.com/jyn514
- RustWeek 2026: 2026.rustweek.org
- Ferrous Systems: ferrous-systems.com
- Ferrocene, the qualified Rust compiler: https://ferrocene.dev/
- The FLS, the Rust language specification: github.com/rust-lang/fls
- The proposed LLM policy for rust-lang/rust: github.com/rust-lang/rust-forge/pull/1040
- docs.rs: https://docs.rs/
- Cranelift: https://cranelift.dev/
- Typst: https://typst.app/
- Hexcat, where Jana Dönszelmann is exploring code coverage for the compiler: https://hexcat.nl/
Interested in contributing to Rust? If you find something that's broken and you're willing to help out, you will keep getting asked to help out.
Interview conducted by Pete LeVasseur on behalf of the Rust Project Content Team.
Find Pete at:
- github.com/PLeVasseur
- https://bsky.app/profile/petelevasseur.com
At RustWeek 2026, the Rust Project Content Team talks with Jynn Nelson of Ferrous Systems about safety-qualifying the Rust compiler, a code coverage murder mystery, consensus building, and the Rust Project's emerging policy on LLM contributions.
Jynn shares how trying to fix a broken "go to latest version" button on docs.rs in 2019 turned into fixing the whole docs.rs build, joining the docs.rs team, and seven years in the Rust Project since. Topics include:
- What Ferrocene's safety qualification and certification work adds on top of Rust's built-in guarantees: external assessment by TÜV, line coverage across the certified core subset, and a semantic diff reviewed every release
- Why Ferrocene releases every three months instead of yearly: staying close to upstream Rust so users never have to choose between the qualified compiler and the latest features
- Qualifying a compiler without a standardized Rust language specification: writing your own specification and testing against it, which became the FLS, now maintained in the Rust Project
- The code coverage murder mystery behind Jynn's talk: three or four overlapping bugs bad enough to delay the first certified-core release, and fixing each layer so it can never happen again
- Consensus building and debugging as the same skill: breaking a hard problem down and asking "where would I start?", plus Jynn's six-hour "How to learn hard things" workshop
- The proposed rust-lang/rust LLM policy: allowing LLMs for debugging, review, and discovery; holding LLM-authored code to a higher standard than human code; and requiring your own words in PR descriptions and comments
- Why completing good first issues with an LLM defeats their purpose, and why people should put more back into the commons than they take out
Jynn's RustWeek 2026 talk, "Precise, consistent, and reliable code coverage": youtube.com/watch?v=P9lmSc4oLFs
Links and resources:
- Jynn's blog: https://jyn.dev/
- Jynn on GitHub: github.com/jyn514
- RustWeek 2026: 2026.rustweek.org
- Ferrous Systems: ferrous-systems.com
- Ferrocene, the qualified Rust compiler: https://ferrocene.dev/
- The FLS, the Rust language specification: github.com/rust-lang/fls
- The proposed LLM policy for rust-lang/rust: github.com/rust-lang/rust-forge/pull/1040
- docs.rs: https://docs.rs/
- Cranelift: https://cranelift.dev/
- Typst: https://typst.app/
- Hexcat, where Jana Dönszelmann is exploring code coverage for the compiler: https://hexcat.nl/
Interested in contributing to Rust? If you find something that's broken and you're willing to help out, you will keep getting asked to help out.
Interview conducted by Pete LeVasseur on behalf of the Rust Project Content Team.
Find Pete at:
- github.com/PLeVasseur
- https://bsky.app/profile/petelevasseur.com






![Yuri Astrakhan Interview, Rivian VW Tech; MapLibre Cofounder [Rust Project Content @ RustConf 2025]
Yuri Astrakhan has had an enviable career. While working as a Principle Software Engineer at Elastic he cofounded the MapLibre project: a library for embedding scrollable maps in websites and native applications with a Rust core. He was then hired by Rivian to work on both internal and open-source software but little did they know that they were also hiring a chief Rust evangelist! The topic of his RustConf 2025 talk was a report on how driving Rust adoption at a large and distributed automotive company has been going; some tips and best practices.
Yuri took some time out of his RustConf 2025 week to sit down with the t-content team and speak to us more about Rust in automotive, encouraging adoption in a large engineering organization, and how open-source can help companies and how companies can help open-source.
Yuris RustConf 2025 Talk: https://www.youtube.com/watch?v=3RIxy9YE-Yk
Yuri Astrakhan: https://github.com/nyurik
MapLibre: https://maplibre.org/
Rivian Volkswagen Group Technologies: https://rivianvw.tech/
Follow @rustvideos for our upcoming video interviews!
Interviewer: Xander Cesari (https://github.com/MerrimanInd) Yuri Astrakhan Interview, Rivian VW Tech; MapLibre Cofounder [Rust Project Content @ RustConf 2025]](https://i.ytimg.com/vi/MgGsZmBNLO0/mqdefault.jpg)



