Keeping Code Consistent
summary
Company migrates core infra to Elixir + Phoenix migration, uses Credo and Dialyzer checks plus ExCoveralls and CI hooks to enforce style, types and coverage. Onboard time averages two to three weeks. During the NFL Draft peak the system serves ~30k concurrent users with response times around 100 ms. OEmbed service rewritten in Elixir removes exponential timeouts, first Elixir app attracts 23 contributors, OEmbed 12, metadata app 10, and production deployment proves reliable.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:27Why Elixir
- 3:50Phoenix Guidelines
- 6:41Elixir
- 7:58Collaboration Barrier
- 13:15Type Stuff
- 14:42Errors
- 16:02Dialyzer
- 17:27Documentation
- 18:54Testing
- 20:32Measuring Coverage
- 20:55Coveralls
- 22:21Full Requests
- 23:14Code Reviews
- 24:13Service Reviews
- 25:11Focus on the Code
- 27:59Measuring Success
- 28:24Is It Worth It
- 28:56Application
- 29:06NFL Draft
- 33:33Highest Concurrent Users
- 34:21How did we fare
- 35:52Testing to take person
- 36:47The point of code consistency
- 37:26Metadata app
- 38:30Adoption book
related talks
40mBeyond your daily coding
47mGood behaviour: Cultivating Healthy Elixir Teams & Codebases
01h 01mArchitecture Decisions: A Case Study -
45mKeynote: One Monolith, Many Teams: Growing an Org...
59mKeynote: Elixir Should Take Over the World
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
29mHacking Development Culture: Treating Developers As People
57mMaximising Side Effects When Adopting Functional Programming