Also available:
Slides: Let's Talk Process Dictionary - Speaker Deck
Code: GitHub - gvaughn/process_dictionary_talk: 'Let's Talk Process Dictionary" talk given at Lonestar ElixirConf 2018 · GitHub

Of course this is right, of course, but I do feel like consciously dividing up pure and impure concerns in your Elixir programs is a powerful design tool. I have been hugely inspired by Gary Bernhardt’s Functional Core, Imperative Shell and @sasajuric’s To Spawn or not to Spawn.

We don’t get all the way to Elm’s side-effect free runtime, obviously, but knowing exactly where those lines our for your own code is a very powerful design strategy. I feel this is why you so heavily advocate—in the talk—for isolation of process dictionary code (preferably in one function).

I hear you though. Elixir’s not pure and it never will be. But I sure learned a ton about how to write Elixir code that I could manage by playing with pure languages.

Looks like a great talk Greg - and I love see references to things said on the forum