web02.fireside.fm Tue, 14 Apr 2026 10:53:08 -0500 Fireside (https://fireside.fm) Elixir Outlaws - Episodes Tagged with “Design” https://elixiroutlaws.com/tags/design Thu, 09 Sep 2021 12: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 101: Bright and Tight http://elixiroutlaws.com/101 799417be-1f7b-49a9-a62c-41c4167cfc36 Thu, 09 Sep 2021 12:00:00 -0400 Elixir Outlaws full Elixir Outlaws The main topic this week is error handling. 27:14 no This week, Chris and Amos discuss error handling and when its appropriate to "Let It Crash" :tm:. A transcript for this episode is available on Binary Noggin's website: https://binarynoggin.com/blog/episode-101-bright-and-tight/ elixir, erlang, BEAM, error handling, elixir design This week, Chris and Amos discuss error handling and when its appropriate to "Let It Crash" :tm:.

A transcript for this episode is available on Binary Noggin's website: https://binarynoggin.com/blog/episode-101-bright-and-tight/

Support Elixir Outlaws

]]> This week, Chris and Amos discuss error handling and when its appropriate to "Let It Crash" :tm:.

A transcript for this episode is available on Binary Noggin's website: https://binarynoggin.com/blog/episode-101-bright-and-tight/

Support Elixir Outlaws

]]> Episode 99: Big Tubes http://elixiroutlaws.com/99 f9b3c321-d718-4fe1-b4fd-c8733c175c9d Mon, 09 Aug 2021 11:00:00 -0400 Elixir Outlaws full Elixir Outlaws The main topic this week is behaviours and protocols. 41:46 no The main topic this week is behaviours and protocols and when to use both. Chris, inspired by the wisdom of Quinn Wilton, thinks that its probably incorrect to use Behaviours to define public interfaces for APIs. Protocols seem to fit the bill better. Both hosts agree that the best kind of dependency injection is just called, "passing arguments to functions". A transcript is available for this episode on Binary Noggin's website: https://binarynoggin.com/blog/episode-99-big-tubes/ elixir, erlang, BEAM, behaviours, protocols The main topic this week is behaviours and protocols and when to use both. Chris, inspired by the wisdom of Quinn Wilton, thinks that its probably incorrect to use Behaviours to define public interfaces for APIs. Protocols seem to fit the bill better. Both hosts agree that the best kind of dependency injection is just called, "passing arguments to functions".

A transcript is available for this episode on Binary Noggin's website: https://binarynoggin.com/blog/episode-99-big-tubes/

Support Elixir Outlaws

Links:

]]> The main topic this week is behaviours and protocols and when to use both. Chris, inspired by the wisdom of Quinn Wilton, thinks that its probably incorrect to use Behaviours to define public interfaces for APIs. Protocols seem to fit the bill better. Both hosts agree that the best kind of dependency injection is just called, "passing arguments to functions".

A transcript is available for this episode on Binary Noggin's website: https://binarynoggin.com/blog/episode-99-big-tubes/

Support Elixir Outlaws

Links:

]]> Episode 80: The ish is what matters http://elixiroutlaws.com/80 60a52314-33b9-4828-b4ea-314681c5b750 Thu, 13 Aug 2020 11:00:00 -0400 Elixir Outlaws full Elixir Outlaws The main topic this week is modeling problems with data and the dangers of the single global process. 36:38 no This week starts with a discussion of Dungeons and Dragons and how great it is. Amos and Chris agree that roll20 is janky, but - like emacs - it’s lovably janky. The main discussion is about modeling problems using data structures instead of processes. The guys agree that manipulating data with pure functions is a good thing and that the tricky part is where to put this data when you’re done. Chris cautions against the desire to put all of your data into a single global process. Databases are sucky global variables, but at least they’re global variables with rules. A transcript is available for this episode on Binary Noggin's website: https://binarynoggin.com/blog/episode-80-the-ish-is-what-matters/ elixir, erlang, BEAM This week starts with a discussion of Dungeons and Dragons and how great it is. Amos and Chris agree that roll20 is janky, but - like emacs - it’s lovably janky.

The main discussion is about modeling problems using data structures instead of processes. The guys agree that manipulating data with pure functions is a good thing and that the tricky part is where to put this data when you’re done. Chris cautions against the desire to put all of your data into a single global process. Databases are sucky global variables, but at least they’re global variables with rules.

A transcript is available for this episode on Binary Noggin's website: https://binarynoggin.com/blog/episode-80-the-ish-is-what-matters/

Support Elixir Outlaws

Links:

]]> This week starts with a discussion of Dungeons and Dragons and how great it is. Amos and Chris agree that roll20 is janky, but - like emacs - it’s lovably janky.

The main discussion is about modeling problems using data structures instead of processes. The guys agree that manipulating data with pure functions is a good thing and that the tricky part is where to put this data when you’re done. Chris cautions against the desire to put all of your data into a single global process. Databases are sucky global variables, but at least they’re global variables with rules.

A transcript is available for this episode on Binary Noggin's website: https://binarynoggin.com/blog/episode-80-the-ish-is-what-matters/

Support Elixir Outlaws

Links:

]]> Episode 79: Providing Value http://elixiroutlaws.com/79 a9268244-686c-49a7-8aed-bfaba90b2573 Thu, 06 Aug 2020 11:00:00 -0400 Elixir Outlaws full Elixir Outlaws This week Chris and Amos discuss keyboards, contracting, and what it means to focus on "quality". 1:01:53 no Chris wants a new, costly keyboard and is willing to use ad hoc justifications to acquire it. Amos thinks its totally reasonable which means its either totally reasonable or totally not reasonable. The conversation turns to contracting and how contracting is different than working for a product company (beyond the obvious tax implications). Chris believes that product companies only pay contractors when they absolutely have to. The main topic this week is software quality, if thats even a real thing, and if it is, how do we get more of it? A transcript is available for this episode on Binary Noggin's website: https://binarynoggin.com/blog/episode-79-providing-value/ elixir, erlang, BEAM, software quality, software design Chris wants a new, costly keyboard and is willing to use ad hoc justifications to acquire it. Amos thinks its totally reasonable which means its either totally reasonable or totally not reasonable.

The conversation turns to contracting and how contracting is different than working for a product company (beyond the obvious tax implications). Chris believes that product companies only pay contractors when they absolutely have to.

The main topic this week is software quality, if thats even a real thing, and if it is, how do we get more of it?

A transcript is available for this episode on Binary Noggin's website: https://binarynoggin.com/blog/episode-79-providing-value/

Support Elixir Outlaws

Links:

]]> Chris wants a new, costly keyboard and is willing to use ad hoc justifications to acquire it. Amos thinks its totally reasonable which means its either totally reasonable or totally not reasonable.

The conversation turns to contracting and how contracting is different than working for a product company (beyond the obvious tax implications). Chris believes that product companies only pay contractors when they absolutely have to.

The main topic this week is software quality, if thats even a real thing, and if it is, how do we get more of it?

A transcript is available for this episode on Binary Noggin's website: https://binarynoggin.com/blog/episode-79-providing-value/

Support Elixir Outlaws

Links:

]]> Episode 55: Refactoring is a dumb word http://elixiroutlaws.com/55 395fda60-5873-4b24-924d-a755a284353c Thu, 03 Oct 2019 14:00:00 -0400 Elixir Outlaws full Elixir Outlaws This week the hosts discuss Strangeloop, Unison, handling breaking changes, refactoring and how to build open systems. 49:25 no This week the hosts discuss Strangeloop, Unison, handling breaking changes, refactoring and how to build open systems. elixir, erlang, BEAM, refactoring This week the hosts discuss Strangeloop, Unison, handling breaking changes, refactoring and how to build open systems.

Support Elixir Outlaws

Links:

]]> This week the hosts discuss Strangeloop, Unison, handling breaking changes, refactoring and how to build open systems.

Support Elixir Outlaws

Links:

]]> 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

]]> Episode 37: Why is it called an everything bagel? http://elixiroutlaws.com/37 d02b1ec7-794c-4d90-b2a6-2c9ae3cc67e5 Thu, 18 Apr 2019 14:00:00 -0400 Elixir Outlaws full Elixir Outlaws This week Amos and Chris discuss prepping for talks and the ways that OTP get misused. 1:02:41 no This week kicks off with Chris chastising Amos about always being late. The hosts discuss the value of time and recent conference trips. The discussion shifts towards talk preparation techniques, the value of speaking at conferences, and some tips for new speakers. Chris takes control of the show and does a hard pivot towards the main topic this week; the overuse of processes and state management. Chris explains that most people can get by with a lot less OTP then they think. He and Amos discuss ways that they see OTP misused or overused, the nature of scaling systems and the dangers of building stateful services. elixir, OTP, erlang, conference speaking This week kicks off with Chris chastising Amos about always being late. The hosts discuss the value of time and recent conference trips. The discussion shifts towards talk preparation techniques, the value of speaking at conferences, and some tips for new speakers.

Chris takes control of the show and does a hard pivot towards the main topic this week; the overuse of processes and state management. Chris explains that most people can get by with a lot less OTP then they think. He and Amos discuss ways that they see OTP misused or overused, the nature of scaling systems and the dangers of building stateful services.

Support Elixir Outlaws

]]> This week kicks off with Chris chastising Amos about always being late. The hosts discuss the value of time and recent conference trips. The discussion shifts towards talk preparation techniques, the value of speaking at conferences, and some tips for new speakers.

Chris takes control of the show and does a hard pivot towards the main topic this week; the overuse of processes and state management. Chris explains that most people can get by with a lot less OTP then they think. He and Amos discuss ways that they see OTP misused or overused, the nature of scaling systems and the dangers of building stateful services.

Support Elixir Outlaws

]]> Episode 33: Highfalutin design techniques http://elixiroutlaws.com/33 f64d3a2a-8f25-4bb2-90fc-85b1b53b35b0 Fri, 01 Mar 2019 12:00:00 -0500 Elixir Outlaws full Elixir Outlaws This week Chris and Amos discuss umbrella apps. 56:28 yes This week kicks off with some standard dad-cast about kids, eye glasses, and problems with being dizzy. Chris tries to steer the conversation towards the main topic of the week: Umbrella apps. Chris and Amos provide some context for umbrella apps and explain the ways that people tend to use them. Chris talks about his experience building phoenix applications and what he values when designing systems. Anna joins half-way through and provides an impromptu opinion on umbrella applications. She provides a status update on the goings on of San Francisco and its current weather patterns. Chris and Amos finish up with a recap of their discussions and some ways that they grow systems over time. elixir This week kicks off with some standard dad-cast about kids, eye glasses, and problems with being dizzy. Chris tries to steer the conversation towards the main topic of the week: Umbrella apps. Chris and Amos provide some context for umbrella apps and explain the ways that people tend to use them. Chris talks about his experience building phoenix applications and what he values when designing systems.

Anna joins half-way through and provides an impromptu opinion on umbrella applications. She provides a status update on the goings on of San Francisco and its current weather patterns.

Chris and Amos finish up with a recap of their discussions and some ways that they grow systems over time.

Support Elixir Outlaws

]]> This week kicks off with some standard dad-cast about kids, eye glasses, and problems with being dizzy. Chris tries to steer the conversation towards the main topic of the week: Umbrella apps. Chris and Amos provide some context for umbrella apps and explain the ways that people tend to use them. Chris talks about his experience building phoenix applications and what he values when designing systems.

Anna joins half-way through and provides an impromptu opinion on umbrella applications. She provides a status update on the goings on of San Francisco and its current weather patterns.

Chris and Amos finish up with a recap of their discussions and some ways that they grow systems over time.

Support Elixir Outlaws

]]> Episode 28: Devoid of joy http://elixiroutlaws.com/28 1a694f01-e9eb-4405-941e-47d0d8c6426a Sun, 20 Jan 2019 16:00:00 -0500 Elixir Outlaws full Elixir Outlaws This week the hosts discuss rust, design of apis, and ways to design away state. 32:43 no 4th wall break Hey y’all it’s Chris. Just wanted you to know that we had a bunch of technical issues with this call. Both mine and Anna’s recordings were corrupted somehow. We’re still looking into why. Because of this the audio quality changes at around the 20 minute mark. We fell back to using the zoom call audio which we typically only use as a reference for lining up all of the other tracks. I just wanted you to know in case you’re sensitive to that kinda thing. Notes This week kicks off with a discussion of the holidays, the plight of climate change, and the impending loss of Florida. Amos steers the conversation back towards elixir and his experience building a shell for his current client. Chris describe’s his current experience writing Rust. While he acknowledges that Rust is a good language he doesn’t feel like Rust elevates the paradigm of programming enough. Amos asks the other hosts what they look for in packages or libraries. This leads to a discussion of how to design deeper apis while leveraging stateless operations. Chris explains how they’re using stateless patterns in vapor. Elixir cards are available by tweeting at @elixiroutlaws (https://twitter.com/ElixirOutlaws) and @elixircards (https://twitter.com/elixircards) on twitter with the hashtag #vapor. You can explain to Chris why he's wrong about rust or whatever. The Elixir Outlaws now have a Patreon (https://www.patreon.com/user?u=5332239). If you’re enjoying the show then please consider throwing a few bucks our way to help us pay for the costs for the show. elixir, rust 4th wall break

Hey y’all it’s Chris. Just wanted you to know that we had a bunch of technical issues with this call. Both mine and Anna’s recordings were corrupted somehow. We’re still looking into why. Because of this the audio quality changes at around the 20 minute mark. We fell back to using the zoom call audio which we typically only use as a reference for lining up all of the other tracks. I just wanted you to know in case you’re sensitive to that kinda thing.

Notes

This week kicks off with a discussion of the holidays, the plight of climate change, and the impending loss of Florida. Amos steers the conversation back towards elixir and his experience building a shell for his current client. Chris describe’s his current experience writing Rust. While he acknowledges that Rust is a good language he doesn’t feel like Rust elevates the paradigm of programming enough. Amos asks the other hosts what they look for in packages or libraries. This leads to a discussion of how to design deeper apis while leveraging stateless operations. Chris explains how they’re using stateless patterns in vapor.

Elixir cards are available by tweeting at @elixiroutlaws and @elixircards on twitter with the hashtag #vapor. You can explain to Chris why he's wrong about rust or whatever.

The Elixir Outlaws now have a Patreon. If you’re enjoying the show then please consider throwing a few bucks our way to help us pay for the costs for the show.

Support Elixir Outlaws

]]> 4th wall break

Hey y’all it’s Chris. Just wanted you to know that we had a bunch of technical issues with this call. Both mine and Anna’s recordings were corrupted somehow. We’re still looking into why. Because of this the audio quality changes at around the 20 minute mark. We fell back to using the zoom call audio which we typically only use as a reference for lining up all of the other tracks. I just wanted you to know in case you’re sensitive to that kinda thing.

Notes

This week kicks off with a discussion of the holidays, the plight of climate change, and the impending loss of Florida. Amos steers the conversation back towards elixir and his experience building a shell for his current client. Chris describe’s his current experience writing Rust. While he acknowledges that Rust is a good language he doesn’t feel like Rust elevates the paradigm of programming enough. Amos asks the other hosts what they look for in packages or libraries. This leads to a discussion of how to design deeper apis while leveraging stateless operations. Chris explains how they’re using stateless patterns in vapor.

Elixir cards are available by tweeting at @elixiroutlaws and @elixircards on twitter with the hashtag #vapor. You can explain to Chris why he's wrong about rust or whatever.

The Elixir Outlaws now have a Patreon. If you’re enjoying the show then please consider throwing a few bucks our way to help us pay for the costs for the show.

Support Elixir Outlaws

]]>