Lessons learned from Elixir Learning Paths
summary
Describes a company-led Ruby→Elixir transition that dedicates two months per engineer, produces 18 new engineers in three months, creates an engineer chapter for shared docs and meetings, and shifts the codebase to more Elixir than Ruby. Recommends tools: Exercism, Elixir School, book clubs and Elixir Lab live streams on YouTube for Portuguese learners. Explains cognitive lessons: working memory limits 2–6 items, importance of spaced repetition, retrieval practice, pair programming, code review and small toy projects to build fluency.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:52LEARNING PATHS
- 2:49LEARNING PATH VS SELF-STUDY
- 7:53PRACTICAL OBJECT-ORIENTED DESIGN
- 8:32SPACED LEARNING
- 10:58Retrieval Practice Actively trying to remember information to make information stick in your memory better
- 12:06FOCUSED AND DIFFUSE MODE
- 14:36COGNITIVE LOAD
- 19:10READING CODE TOGETHER
- 20:37Reading Code is an important skill
- 23:15PAIR CODE REVIEW
- 24:27WRITE CODE
- 24:55COMMUNITY SUPPORT
- 29:15ENGINEERING CHAPTER
- 30:04ELIXIR LAB
- 32:02Learning Path can be an interesting tool to support your Elixir adoption strategy
- 33:48Continuous Learning is important
- 34:01Learn how to learn
related talks
36mLessons learned from Elixir Learning Paths
19mFrom Bootcamp to Contracts in Elixir
38mLearning Erlang and Elixir(..)Exercism and Advent of Code
49mTeaching functional programming to noobs
06mLT: The Elixir Hiring Paradox
38mJoy - Maintaining Passion for Programming
28mHow Elixir Helped Me to Love the Back End
19mPanel: Elixir Adoption