Stay ConnectedJoin our weekly discussion of the popular functional language built on top of the Erlang virtual machine. Each week, we discuss the world of Elxiir, Phoenix, OTP, and then BEAM.
Become a supporter of this podcast: https://www.spreaker.com/podcast/elixir-mix–6102049/support.
Copyright: © 2018 Intentional Excellence Productions, LLC
In this episode of the Mix the panelists talk about Seniority. They lay out their own personal journeys towards getting a senior title and how they define seniority for themselves - especially how it goes beyond the ability to write code well.
Among other things they discuss:
In today’s all-panelist episode, we take a shot at demystify domain-driven design. We discuss several books and some concepts that stand out in those texts. How easy or hard do Elixir and Phoenix make it to apply DDD principles? We give our experience with taking these concepts and putting them into practice, and give some tips and resources for getting started.
Some of the topics covered:
Today Adi, one of our hosts and the hiring manager at Elixir, talks about the intricacies of applying for a job, and what companies to search out. We talk about the expectations for the applicant, and how to prepare. We also talk about what you can look for the employer to provide before spending too much of your time in the interview process. Walking through various interview processes, we learn what things can help you land the job you want.
Companies that are hiring Elixir positions (google or reach out to Adi):
In this episode the panel talks to Danny Hawkins - CTO at Quiqup - and his team's journey at Quiqup with Elixir. Danny explains how some of the first things Quiqup built were using Elixir and how they then left Elixir behind in favor of TypeScript, only to come back to Elixir.
The panel considers how these choices rarely are purely driven by technological qualities but instead have to factor in cultural- and knowledge-aspects of a team, and how a top-down dictated technology decision - even if there are good reasons for it - can be harmful to a team's morale.
Get in touch with Danny via email! Click here.
Sponsors
Today we talk with Abul Asar Sayyad, a software engineer from Mumbai, India. Working for ID Plans, a commercial property management solution. We discuss his blog article about combining GraphQL with LiveView for rendering on the front end. We also dive into GraphQL libraries, working with LiveView, and testing.
Sponsors
In this episode Adi and Sascha dig deeper into what it means to consume and build APIs in Elixir and how a RESTful approach compares to choosing GraphQL as your weapon of choice. Along the way they discuss common pitfalls when building APIs (spoiler: one is caching), how to test all of this, and what their personal preferences and experiences are in creating APIs in Elixir.
Sponsors
Bad documentation wastes time, costs real money, and makes developers unproductive. Documentation might be bad because it is flat-out wrong (typos, references to an older version, etc.), but more often documentation is bad when it fails to tell us what we need to know. Don’t let all your hard work go to waste because you failed to communicate what your software is or how to use it. Today on the show, Everett Griffiths shares his insights on how to approach documentation simply and effectively.
In this episode…
In this week’s all-panelist episode, Sascha and Allen tackle the topic of concurrency on The Beam. They discuss parallelism, some things to do and some not to do, and some of the questions and issues that arise.
Sponsors
David van Leeuwen joins the show to share his perspective about error handling with Phoenix’ LiveView form and keeping implementations that are used to render an input as simple as possible. He also discusses his career progressions with Elixir and other various languages, plus why and how he built his latest project, Mave.io.
Sponsors
In this episode Simon Zelazny joins the mix to talk about his experience in scaling an Elixir and Phython based service to meet a once-in-a-blue-moon demand scenario. The panel and him discuss the challenges in finding the relevant bottlenecks in non-trivial software systems - and BEAM applications in particular - and what options there are to fix those.
They also discuss pragmatism in the context of software development, and how we as software developers are not paid to write pretty code but to solve business problems, which might also mean to choose NOT to build on top of the BEAM, if circumstances demand it.
Sponsors
Our TOPPODCAST Picks 
