Elixir Outlaws

4th wall break: Hey y'all audio from this week is a little worse then usual. We needed to use the backup audio file for technical reasons. Just wanted to provide a heads up. -keathley Show notes This weeks starts with a discussion of how to have meaningful conversations about design decisions. Chris asks whether programming best practices are for individuals or for teams. This leads to a discussion about team dynamics and how to facilitate productive conversations in teams. The hosts end with some tips on facilitating better communication and openness in team environments.

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.

This week the original friend of the show, Fred Hebert, joins the hosts for a wandering discussion, ostensibly about his fantastic new book Property-Based Testing with PropEr, Erlang, and Elixir: Find Bugs Before Your Users Do by Fred Hebert | The Pragmatic Bookshelf (https://pragprog.com/book/fhproper/property-based-testing-with-proper-erlang-and-elixir) Fred discusses his motivations for writing, maven plugins, and how to write better property based tests. He also shares some opinions on code coverage, test driven development, and elixir’s pipe operators. 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. Special Guest: Fred Hebert.

This week the hosts are joined by special guest, friend of the show, and author of Elixir in Action Saša Jurić. The conversation kicks off with a discussion of protein poisoning before quickly turning to Elixir in Action. Saša explains his motivation and process for writing. After this the conversation moves towards Saša’s custom CI service he’s been building. Saša explains the major benefits of using elixir and erlang for these sorts of tasks. He talks about his dream of being able to utilize erlang with no other dependencies. 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. Special Guest: Saša Jurić.

This week we dive into Amos’s frustrations with emacs. Chris talks about the nature of optimizers and how addictive micro-optimizing can be. There's a lot of bird trailing before the main topic kicks off around 18:25. The main topic this week is Private Modules. Chris doesn’t think his opinion matters but Amos wants to talk about it anyway. Amos doesn’t know why we need this so Chris tries to provide some context. This eventually leads to a conversation on warnings and how they get surfaced in Elixir. Chris maintains that he’s ambivalent and Amos wants to think about it more. At the end of the show Chris provides some pretty great tips for getting over stage fright before a talk. 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.

This week Amos is looking for a new client and visiting lots of museums. The discussion turns to common libraries and methods when starting new projects. This leads to the topic of how to do effective handoff with clients through pairing and creating psychological safety in teams.

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 leveragi

This week kicks off with a discussion on the merits of being punctual and valuing people’s time. The conversation takes a detour into Chris and Amos’s experiences working at the big blue rectangle known as Walmart. This leads into the main topic for this week which is unit testing. Amos starts off with some definitions and Chris explains why if you’re gunna write a unit test you should actually be writing property based tests. The hosts wrap up the discussion by weighing the tradeoffs of different styles of testing. 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.

This week kicks off with a discussion of the holidays and the drama of having kids. There's a lot of shucking and jiving before leading into the main topic of this week: Interesting things that could be added to elixir. They discuss features for the IO and Enum modules, wacky ideas for functional composition and hopes for the community in the coming year.

This week the hosts talk with Andrew Summers about the recent improvements to dialyixir and how to incorporate it into elixir applications. Special Guest: Andrew Summers.

This week Jose Valim joins the outlaws to answer questions from the community. The conversation starts with a discussion about the current state of dialyzer and future plans to add a type system to elixir. Jose laments some of the decisions to include dialyzer types directly into Elixir. This leads to a discussion of new tools being built for deployment and for metrics gathering. Chris asks about efforts to make it easier to use elixir libraries in erlang and ways that we might be able to share more libraries across ecosystems. Jose discusses plans for extending the functionality of GenStage and Flow in order to help people build more robust data pipelines. Finally, Jose describes his recent adventures into livestreaming and tries to convince the hosts to livestream the podcast. Special Guest: Jose Valim.

This week Anna and Chris decompress from GigCity Elixir. They discuss several of the talks including a talk by Stu Halloway about what open source maintainers owe to communities. This leads to a discussion on how to have productive conversations about open source projects. Chris laments some of the ways that he's interacted with the community and Anna pushes for ways to facilitate constructive communication. This leads to a discussion about good ways to build modules and libraries that can be easily taught to newcomers. A copy of this episode is available to read as a blog, here: https://binarynoggin.com/blog/episode-23-reaching-understanding/

Special Guest: Dave Thomas.

This week the hosts are joined by special guest and Friend of The Show :tm: James Edward Gray II. After introducing themselves for the first time in the shows history, James presents several questions for the guests. This leads into a discussion about dependencies, when we should rely on them, and how we should evaluate them. James turns the conversation to a discussion about Anna and Chris's talks at GigCityElixir. Special Guest: James Edward Gray II.

This week starts off with a discussion about Amos and Chris’s recent trip to Strangeloop and the great talks they saw there. There’s a brief interlude into airports and the World Famous sponge display in the Chattanooga airport. The main topic this week: How do we handle complexity when designing software. Chris, excited after reading Philosophy of Software Design, gets exceptionally fired up about software design and the tradeoffs that programmers make. The hosts discuss the nature of software developers and the ways that programmer culture influences those decisions. The hosts turn to discussing the recent changes in Ecto which is mostly Chris ranting for 15 minutes because he doesn’t get it (those who dislike rants will want to turn off their podcast players).

foot marbles moving ElixirConf

Special Guest: Paul Schoenfelder.

Distillery 2.0 Open source life Special Guest: Paul Schoenfelder.

This week Amos and Chris discuss a fun absinthe bug and try to determine how to pronounce "leex". Chris describes his frustrations with REST and why building clients for REST apis is probably the worst thing ever. In the main topic this week, Amos expresses his frustration with Purely Functional Data Structures and understanding amortized time analysis. Chris attempts to provide some clarity by describing the physicists method.

This week Anna and Amos are joined by Nerves core team member Connor Rigby. They discuss nintendo hacking, robotic farming and how to get started with nerves development. Special Guest: Connor Rigby.