How Elixir Helped Me to Love the Back End
summary
A JavaScript-focused developer switches to Elixir and finds the backend suddenly clear and enjoyable: generating a working app with mix phoenix.new in a few commands, following data flow with pattern matching, multiple function heads and piping, and relying on Elixir’s readable error messages. Test-driven development and writing tests surface exact failures so fixes follow the flow. Real projects include enqueuing emails instead of sending from the client and a React front end talking to Phoenix with Phoenix LiveView sockets, and the backend now feels maintainable and rewarding.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:49Front-end to back-end neglect
- 3:15Discovering Elixir through a unique job application
- 5:05Learning Elixir as new language
- 7:36Elixir community culture
- 9:01First Phoenix and syntax impressions
- 11:14Elixir and back-end testing
- 13:47Loved back-end logic all along
- 15:32Why Elixir is mechanic-friendly
- 18:20Balancing dev and user needs
- 19:26Conclusion and future
- 20:11Q&A
- 21:19Front-end influencing back-end
- 23:10Psychology shaping development
- 24:58Career change and accessibility
- 28:09Closing remarks
related talks
19mPanel: Elixir Adoption
36mLessons learned from Elixir Learning Paths
27mHow Elixir is driving Australian product innovation- 36mLessons learned from Elixir Learning Paths
39mMoving to Elixir from Ruby
19mFrom Bootcamp to Contracts in Elixir
06mLT: The Elixir Hiring Paradox
33mLearn a new language using TDD and Clean Code