How to (not) introduce Rust at your workplace - a tale
summary
Attempts to introduce Rust start with a concrete side project: a Grafena annotations datasource built with CI/CD, Docker and deployed to Kubernetes that runs in production; a second stream processor using a high-performance crate delivers impressive throughput; the third microservice collapses under generated RPC toolchain pain and Rocket/diesel nightly breakage as dependencies drift. Lessons: prefer fewer moving parts, use cloning as training wheels while learning ownership, beware zero-cost abstractions that complicate maintenance, and prioritize explicit buy-in and empathy.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:26story time
- 1:40stream processing
- 4:40processing networking metrics
- 5:42processing CPU metrics
- 7:25Rust Evangelism Strike Force?
- 9:37prometheus metrics
- 11:33how about IDE support
- 12:33parsing a binary protocol
- 12:50impressive performance results
- 13:03the third project
- 14:18sharks tornadoes diesel-powered rockets pineapple pizza
- 15:38ZERO cost ABSTRACTIONS
- 15:57ZERO working software
- 20:16REALITY CHECK
- 21:41established patterns
- 23:19too excited about Rust?
- 26:08empathy is a POWERFUL feature
related talks
01h 27mRust in Academia and Introduction to Iron
28mRust for Pythonistas
38mPanel: Rust in reality
20mMastering Rust on Edge and Cloud — AI/IoT Case Studies
54mHelp, my whole team started coding in Rust
46mPanel: What has to change to increase Rust adoption in industrial companies?
01h 42mIntroduction to Rust (for people who have never used a compiler)
27mHow to switch from cozy NodeJS to scary Rust as a company.