Good behaviour: Cultivating Healthy Elixir Teams & Codebases
summary
Shows a small Letterboxed-style API built with Phoenix and Ecto where preloads move from controllers into a movies context, workers use Oban job enqueues review ID to call a Twitter deliverer, and naming rules (e.g. for_ = filter, with_ = preload) make pipelines readable. Argues that these concrete choices cut cognitive load, speed onboarding, make tests and docs act as clues, and let teams balance fast MVPs with scheduled cleanups using Mix format, Credo and Notion.
AI-written summary · about
chapters (15)
- 0:00Start
- 7:10Code organization
- 8:28Web layer: request routing and response
- 10:43Service layer: coordination and execution
- 11:47Schema: entity definition
- 15:10Separation of concerns
- 15:38Functions
- 20:57Documentation as clues
- 23:01Team patterns
- 24:30Elixir-specific concerns
- 25:22Onboarding
- 26:17the teacher
- 28:21the buddy
- 29:56Maintenance
- 32:12Tooling
related talks
47mElixir for curing product development pains
44mElixir & Phoenix - Fast, Concurrent and Explicit
43mThe River
47mElixir for curing product development pains?
39mKeeping Code Consistent
22mRefactoring Elixir for maintainability
03h 19mWorkshop - All Aboard The Elixir Express!
37mModern Abstractions and the Web, and avoiding Pitfalls because Life is short