Elixir Outlaws Podcast
Amos, Anna and Chris speak at the first-ever ElixirConf Africa.
The Elixir Wizards join the Outlaws for a crossover podcast.
Chris talks about his new job at Frame.io and discusses onboarding onto a new project.
Amos King Anna Neyzberg Chris KeathleyFriends of the Show Franceso Cesarini Daniel Craig The Elixir Outlaws now have a Patreon. If you’re enjoying the show then please...
The Outlaws discuss the morality of making promises you can’t keep, then spend the rest of the episode discussing the ups and downs of past conference talks.
After confirming that there is indeed a Kansas City, Missouri, the Outlaws discuss Amos’ new projects using Phoenix and some LiveView, then opine about CSS, Wallaby, and testing, before closing with brief commentary on Nx.
Chris skipped his normal pre-podcast prep and is trying to make up for it. Amos wants to know more about what Chris does to prep; a topic which is interesting to literally no one. Quotes are misattributed as the hosts turn to the main topic of the week: What makes for good design? Chris claims to have a specific design sense but has no idea if its a good sense or not. Both he and Amos agree that consistency is important and that software developers should always be working to making the design of a system better.
The Outlaws discuss Mnesia and all of the ways that it’s possible to “break it”. Chris and Amos discuss why Mnesia has a bad reputation, where it is a good fit, and how to mitigate some of the issues. Chris has recently become the owner of a 3D printer and he agrees with everyone else: 3D printing is really cool.
This week kicks off with a discussion of Amos’ reading list. Soon, the Outlaws speculate about the Elixir benchmarks José Valim has been teasing. Chris explains his frustration with “modern infrastructure” and programmers choosing complex solutions they don’t need.
Chris has been drawing maps for his Dungeons and Dragons game, and he’s pretty proud of them. Amos is trying to order events and has questions about hybrid logical clocks, leading to a discussion of what ordering even is and why it’s such a problem in distributed systems.