How things are, and how they could be
summary
Claims that Erlang has great primitives but poor workflows get backed by concrete fixes: adoption of rebar3 and relx shortens the time to a release from months or years down to days, Hex provides searchable packages, Dialyzer and property-based testing integrate into CI, and a demo scaffold generates a CRUD app with auto tests docs metrics and about 80% overall coverage and 100% model coverage. The argument centers on shipping reproducible templates, documenting libraries, and removing the repeated manual hacks.
AI-written summary · about
chapters (9)
- 0:00The Erlang challenge
- 1:03Compounded hardships
- 6:16Overcoming institutional inertia
- 9:03Evolution of build tools
- 11:25The boiled frog syndrome
- 13:17Improving the onboarding path
- 18:36Redefining the developer experience
- 26:45Demo: A better project template
- 40:04Q&A and closing thoughts
