Working with Legacy Erlang Code
summary
Practical guidance for maintaining and improving legacy Erlang codebases, focusing on surviving and fixing past poor implementations. Covers techniques and approaches for understanding, refactoring, and stabilizing existing Erlang systems rather than rewriting them from scratch.
AI-written summary · about
chapters (20)
- 0:00Legacy Erlang code
- 1:06Legacy code
- 2:33Code confidence goals
- 4:42Erlang unit testing
- 6:27Test coverage reports
- 8:36CI minimum coverage
- 10:02Erlang code formatters
- 14:26Incremental formatting
- 14:48Elvis tool
- 16:54Elvis failed rules
- 18:21Xref cross-references
- 20:54Dialyzer discrepancies
- 23:01Dialyzer in large projects
- 24:48Incremental Dialyzer fixes
- 26:34Dead code removal
- 27:17Oxbow lakes in code
- 29:05Automatic Erlang docs
- 31:37Confidence tools
- 33:02Other Erlang tools
- 34:50Closing
related talks
52mHow to work with legacy so neither you nor the project burns out
33mThe Divine Comedy of Legacy Code: From Hell to Paradise with Elixir
39mLegacy Code - The Survival School
01h 11mLegacy: Rewrite cannot support
50mMistakes I made working with legacy code and how to fix them
50mWe ♥️ legacy
50mLearn to live with a legacy monolith (or not)
53mCongratulations! Legacy code guru level unlocked!