Skip to content

Instantly share code, notes, and snippets.

@macintux

macintux/patching-erlang-talk.md

Created August 31, 2017 16:46
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save macintux/7c7a36d9d8b0788eeb1d5ec96f0f5635 to your computer and use it in GitHub Desktop.
Save macintux/7c7a36d9d8b0788eeb1d5ec96f0f5635 to your computer and use it in GitHub Desktop.
Download ZIP
Walking the High Wire: Patching Erlang Live (CodeMash 2018 talk proposal)
Raw
patching-erlang-talk.md

Two years ago at CodeMash we discussed how Erlang was a paradigm shift masquerading as a programming language. Last year we illustrated how fun it is to write. This year we show off one of its most powerful aspects: maintaining a production system.

Erlang (and Elixir, its younger sibling) allow you to not only trace the behavior of a production system, but also to query the data in memory, replace your code on the fly once you've found the problem, and fix the data that the old code mishandled, so the system keeps plugging away. Look, ma, no reboots.

Also discussed will be other criminally under-appreciated languages with similar features, because really, can you ever have enough magic tricks in your repertoire?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment