TBA: Developer experience stuff?
summary
New developer experience claims: 80% of tool preference is familiarity, 10% ambition and 10% laziness; every code choice becomes a developer tool. Examples: built Wrangler to deploy Rust‑generated WebAssembly serverlessly on the edge and cargo‑generate; Rust chose the controversial question‑mark operator after moving from verbose match to try! to ?; introduce a strangeness budget and cite Napoleon Dynamite as unpredictable adoption, arguing tradeoffs between terse syntax and newcomer onboarding.
AI-written summary · about
chapters (9)
- 0:00Start
- 5:04WHAT IS YOUR FAVORITE DEVELOPER TOOL?
- 9:13THE "NAPOLEON DYNAMITE" PROBLEM
- 11:38LEARNING TAKES TIME
- 25:32MANUAL
- 29:56WHAT IS A DEVELOPER TOOL?
- 30:52HOW DO YOU DISCOVER THE OPPORTUNITY FOR BETTER DEVELOPER EXPERIENCE
- 33:04I CAN ANTICIPATE HOW API CHOICES AND ABSTRACTIONS IMPACT THE WAY OTHER PEOPLE WOULD SOLVE THE PROBLEM
- 39:25GO FORTH AND ENABLE FIRE MARIOS!
related talks
25m"Compiler-Driven Development: Making Rust Work for You"
32mBuilt With Love - Why Developer Experience Matters
25mLessons Learned From the Rust Ecosystem That Can Be Adopted Elsewhere
28mRust for Pythonistas
23mRebuilding in Rust for Good Reason
50mConfessions of a Rusty Java developer
46mThe future of development: Are our jobs getting harder or easier?
38mMaking Rust Delightful