Code Spelunking for Knowledge and Profit

on YouTube ↗28m

" summary

Code spelunking yields concrete takeaways: how Ecto runs its integration test suites via mix aliases and environment-driven test_paths, how Phoenix watches templates with an external_resource plus a small custom compiler (ten minutes to wire into a library), the reason guards must be explicitly inlined, and that a small utility was contributed upstream (pop_in accepted into Elixir core). Surprising numbers include ~88% of Elixir’s source written in Elixir itself. Patches and repo-level digging actually produce usable fixes, not just theory.

AI-written summary · about

" chapters (8)

1. 0:00Intro
2. 2:01Ecto Integration Tests
3. 4:37Phoenix View Inheritance
4. 8:05Phoenix Template Compilation
5. 14:51Elixir 'pop_in/2
6. 16:06Elixir test module attributes
7. 18:29Elixir guards
8. 21:09Elixir Special Forms

" related talks

• 36mRefactoring Elixir - Lessons Learned from a Year onDevon Estes · ElixirConf EU 2017
• 28mExplicit ElixirPaul Lamb · ElixirDaze 2016
• 34mCode Spelunking: teach yourself how Rails worksJordan Raine · RailsConf 2019
• 40mIntelliJ Elixir Works Even if your Code Doesn'tElle Imhoff · ElixirConf EU 2024
• 32mThe Excitement of ElixirDevin Torres · ElixirConf 2014
• 57mSpeaker PanelChris McCord, Dave Thomas, José Valim, Bruce Tate, Francesco Cesarini, Robert Virding · ElixirConf 2014
• 40mIntelliJ Elixir Works Even if your Code Doesn'tElle Imhoff · ElixirConf EU 2022
• 03mLightning Talks – Sergii BoikoSergii Boiko · ElixirConf EU 2016