Explicit Elixir

on YouTube ↗28m

" summary

A pragmatic case for making code explicit: a modified Luhn credit‑card validator from Rosetta Code demonstrates putting the input at the top of a pipeline, breaking transformations into named functions, and testing the reducer. Examples use Phoenix as a pipeline of plugs, Ecto and Mobius for query building with a query command struct, and Enum (use enum unique instead of hand‑rolled dedupe). A small meetup of about ten people finds these patterns reduce if/elsif complexity and they work.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 10:20Lund Algorithm for Calculating Credit-Card Validity
3. 16:43Pattern Matching
4. 18:04Common Idioms
5. 25:08Getting Set Functions

" related talks

• 36mRefactoring Elixir - Lessons Learned from a Year onDevon Estes · ElixirConf EU 2017
• 28mCode Spelunking for Knowledge and ProfitBrian Cardarella · ElixirConf 2016
• 38mRefactoring Techniques for Elixir, Ecto, and PhoenixGary Rennie · ElixirConf 2016
• 32mThe Excitement of ElixirDevin Torres · ElixirConf 2014
• 33mThe First Few SipsRichard Bishop · ElixirConf 2014
• 45mWhat Elixir is aboutJosé Valim · Erlang User Conference 2015
• 48mKeynote Catalyse ChangeDave Thomas, José Valim · Erlang Factory SF Bay Area 2014
• 48mAnti-Patterns in the WildPaweł Antemijczuk, Maarten Faddegon · Erlang User Conference 2017