Why Companies Hire Developers Who Don't Know Elm
summary
Companies hire non‑Elm developers and train them fast: case studies from Vendr (25 engineers), Corvus Insurance (≈50 engineers, only 10% knew Elm), NoRedInk and Brilliant show newcomers becoming productive within four weeks or even a week after short pairing and onboarding. Elm’s browser‑based editor, progressive package design, beginner‑friendly error messages and small core let non‑programmers ship interactive frontends with far fewer bugs (one reported production crash from debug.todo), enabling lower testing overhead and stable hiring pipelines via companion planting.
AI-written summary · about
chapters (16)
- 0:00Introduction And Motivation
- 2:25Growing Functional Programmers
- 4:15Elm Adoption In Business
- 8:09Case Study: Vendr
- 11:35Case Study: Corvus Insurance
- 15:18Case Study: NoRedInk
- 18:23Case Study: Brilliant
- 20:28Building Functional Programming Pipelines
- 24:28Attracting Developers To Functional Languages
- 25:19Immediacy And Developer Experience
- 26:47Designing Smooth Learning Paths
- 31:43Error Messages And Learning
- 33:43Favorable Comparisons And Adoption
- 35:41Releases, Blogs, And Community Growth
- 41:30Conclusions
- 42:18Audience Q&A
related talks
24mElm — new language, new you
31mMake the Back-End Team Jealous: Elm in Production
47mElm or how I learned to love front end development
39mDeveloper Happiness on the Front End with Elm
16mElm as an antidote to front-end fatigue
26mElm - Frontend with Guarantees
53mElm in production
26mDeveloping with Elm in a large application