web01.fireside.fm Wed, 15 Apr 2026 01:59:39 -0500 Fireside (https://fireside.fm) Elixir Outlaws - Episodes Tagged with “Let It Crash” https://elixiroutlaws.com/tags/let%20it%20crash Thu, 06 Jun 2019 10:00:00 -0400 Elixir Outlaws is an informal discussion about interesting things happening in Elixir. Our goal is to capture the spirit of a conference hallway discussion in a podcast. en-us episodic The hallway track of the Elixir community Elixir Outlaws Elixir Outlaws is an informal discussion about interesting things happening in Elixir. Our goal is to capture the spirit of a conference hallway discussion in a podcast. no elixir, erlang, BEAM Elixir Outlaws amos@binarynoggin.com Episode 42: Carriage Return Line Feed http://elixiroutlaws.com/42 650fac1c-9bc5-4222-a9a7-abea33824c9f Thu, 06 Jun 2019 10:00:00 -0400 Elixir Outlaws full Elixir Outlaws This week Amos and Chris discuss Let it Crash how to think about building resilient systems 50:50 no This week Elixir has been uninstalled from Amos’s laptop and Chris is reading books and writing C. Chris explains why he still chooses to write C and why most people don’t need to manually manage memory. During the main topic Amos describes a problem he’s having with Tesla and Hackney. This leads to a discussion about how to build systems that can handle failure. Amos brings up Let It Crash and where it applies. Chris provides some insights into building stable systems and how supervisors influence design. elixir, erlang, let it crash This week Elixir has been uninstalled from Amos’s laptop and Chris is reading books and writing C. Chris explains why he still chooses to write C and why most people don’t need to manually manage memory.

During the main topic Amos describes a problem he’s having with Tesla and Hackney. This leads to a discussion about how to build systems that can handle failure. Amos brings up Let It Crash and where it applies. Chris provides some insights into building stable systems and how supervisors influence design.

Support Elixir Outlaws

]]> This week Elixir has been uninstalled from Amos’s laptop and Chris is reading books and writing C. Chris explains why he still chooses to write C and why most people don’t need to manually manage memory.

During the main topic Amos describes a problem he’s having with Tesla and Hackney. This leads to a discussion about how to build systems that can handle failure. Amos brings up Let It Crash and where it applies. Chris provides some insights into building stable systems and how supervisors influence design.

Support Elixir Outlaws

]]>