Keynote: Fireside Chat on code design
summary
Argues that BEAM languages shape design by matching mental models to domain needs and by giving concrete tools: supervisors and application structure supply concurrency, fault tolerance and architectural shape; formatter and mix and Hex change coding habits, collaboration and reuse; historical constraint of a 32,000 process VM and the need to serve ~30,000 simultaneous calls explains why early designs conserved processes and later shifted for multicore performance; warns against trying to write object oriented Erlang and against overengineering flexibility that breaks tests.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:25What is design
- 4:03What does design mean to Eric
- 7:26How does language shape the design
- 9:50Accidental complexity
- 17:31Tools and culture
- 22:21How has tooling changed
- 29:33Anti Patterns
- 29:56Own your process
- 33:08Macros
- 34:19Unmute
- 38:19Outro
related talks
47mKeynote: My BEAM history
40mComparison and Commentary on "Application Operating System"
49mKeynote: How to sell Elixir (Again)
02m12 yrs supporting Software Architecture teaching with BEAMs
43mThursday Keynote -- What Programming is Really About
45m12 years supporting Software Architecture teaching with BEAMs
45mKeynote: Inviting Everyone to the Party
47mBEAM Architecture Handbook