Elixir Outlaws Podcast
Anna has a new espresso machine and both Chris and Amos are very jealous. Chris wonders how Anna is going to make good coffee without someone judging her. Amos is hiring employees and wants advice on how to conduct better interviews.
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.
Chris and Amos discuss contracting and how it’s different than working for a product company (beyond the obvious tax implications). Chris believes product companies only pay contractors when they absolutely have to. The main topic this week is software quality, if it’s a real thing, and if it so, how do we get more of it?
Chris solicits feedback from the other hosts on his notion that business logic isn’t a “real thing,” Anna and Amos discuss the degree to which Chris might be a pedant. The show wraps up with a discussion on how to change the way programmers can grow and think differently about problems.
Chris one-sided rant trying to solidify his thoughts on business logic.
Chris talks about his experience after a tornado went through his neighborhood. The Outlaws discuss coffee and building community during Covid.
Amos, Anna and Chris give a keynote at ElixirConfEU.
Chris recently replaced some Ruby with some Elixir. The guys discuss what it takes to rewrite a service, why Elixir is a good choice when you need to do more than one thing at a time, and the benefit of choosing tools that your team understands.
Amos and Chris chat about when to use telemetry instead of sending metrics directly from an app code, leading to a discussion on how Bleacher Report uses telemetry, some established conventions, and how those conventions may be changing.
Amos is joined by Martin Gausby, friend of the show, to talk types, open source projects and emacs.