A qualitative research post from the Rust team exploring how developers learn Rust, based on interviews and surveys conducted as part of the Rust Vision Doc process. Key themes include the many paths into Rust (curiosity, job reassignment, organizational adoption), common stumbling blocks like unlearning OOP habits and 'clone guilt', how the borrow checker is learned through compiler diagnostics and practice, the role of LLMs as learning aids, and organizational strategies for ramping up teams. The post also surfaces 'silent attrition' — learners who quietly walk away — and highlights how community reception shapes who stays. Actionable takeaways include creating learning materials aimed at unlearning prior language habits, making 'clone freely while learning' advice official, and improving the perceived freshness of The Rust Programming Language book.
Table of contents
Many paths to needing RustRust learning resourcesBeginner stumblings and unlearning habitsLearning to work with the borrow checkerMulti-paradigm, but not the OOP some are used toTeaching Rust in academiaLearning using LLMsOrganizational considerations for Rust learnersSilent attritionConclusions188K Impressions7 Comments