Travis Elnicky's guest appearances

Travis Elnicky

Elixir Mix

Devchat.tv Episode Roundup

Phil Toland

Feather Knee

Fernando Hamasaki

Sam Davies

Julien Maisonneuve

Julian Fahrer

Chris Dosé

Yiming Chen

Szymon Soppa

Mariano Guerra

Luca Peppe

Catalina Astengo

John-Daniel Trask

Kevin Moore

Devon Estes

OwlTail

In this week’s episode of Elixir Mix the panel interviews Travis Elnicky, software architect at Podium. Podium is Utah based company that has been using Elixir for three years. Travis explains Podium’s history and its experience adopting Elixir. When Travis started at Podium they were a small startup with, he was their 16th employee. They were using Ruby on Rails and focusing on collecting reviews for local businesses. When they saw a need for a messenger application, they tried a few solutions choosing Elixir because of the familiarity they felt coming from a Rails background. After switching to Elixir, Podium grew rapidly. Now Podium has 700 employees, 130 of whom are engineers. Travis discusses with the panel how things are run over at Podium. Their teams are aligned around products and features. This makes all their engineers' full-stack developers. Podiums teams run with a lot of autonomy, they also have teams that help with internal tooling to tie the products together.The panel is curious about the recruitment process at Podium. Travis explains that their hiring is mostly based on referrals, which they found has been pretty reliable. The panel discusses the value of referrals incentives programs. By hiring referrals they save money placing ads and going to fairs. Referrals tend to be more aware of the job they are going into and already have a friend to help them transition jobs and frameworks.Next, Travis walks through what it is like for a new hire at Podium. After onboarding, the new hire sits down with their team lead and codes, taking it all the way to production. The panel considers the advantages of new hires diving in, whether or not they know Elixir. It introduces them to the work they will be doing, gives them confidence by contributing to the team, and the one on one attention shows them the culture of unity at Podium.Podium has a lot to offers its developers. It has a team whose focus is internal developer experience. Podium maintains a focus on learning and growing in Elixir. They offer training for those who are unfamiliar with Elixir. Once per week, they do a Nerd Lunch, the company buys them all lunch while Podium engineers teach their fellows about software. Elixir 101 training also happens every week and is also taught by Podium engineers. Allowing Podium engineers to teach gives learners a chance to teach which in turn helps them learn. It also allows engineers to network outside their assigned teams. The panel considers how people-centered all the solutions are at Podium. The panel wonders if Podium ever uses outside trainers or services. Travis shares the wonderful experience they have been having by using Plataformatec’s Elixir Development subscription. He says it has been incredible to be able to jump on a call, talk to them and get some feedback. Using the subscriptions allows their senior developers to level up, while the other classes and lunches helps the junior developers to level up. Podium recently sponsored ElixirConf and send a big crowd to a few different conferences every year. Travis explains the value of the conference is not only in the education received by the engineers who get to go. At Podium, the engineers who go to the conferences then come back and present what they learned at the conference, sharing what they think Podium could apply to their stack. This makes the conferences valuable to the entire team. The last topic the panel discusses in the episode is the CI at Podium. The panel explains that most of the feedback for a new developer should be coming from the CI. Travis explains how the CI is set up. When he started they were using Github and has moved to Gitlab. They use credo checks, unit tests, sobelow, and dialyzer. The panel asks about Elixir formatter and how they check format in the CI. Travis explains what he likes about credo and gives tips for running it. The panel has Travis introduces sobelow and what it does for Podium. Dialyzer is considered by the panel, they explain the trade-off of using dialyzer while sharing times that it had saved their bacon.Panelists  Mark Ericksen   Eric Oestrich   Michael Ries  Guest  Travis Elnicky  Sponsors    Sentry– use the code “devchat” for two months free on Sentry’s small plan   Sustain Our Software   Views on Vue   CacheFly  Links  Two Years of Elixir at Podium: Thoughts   https://www.podium.com/    http://pages.plataformatec.com.br/elixir-development-subscription    https://docs.gitlab.com/ee/ci/    https://github.com/rrrene/credo/    https://github.com/nccgroup/sobelow    https://hex.pm/packages/dialyxir    https://hexdocs.pm/mix/master/Mix.Tasks.Format.html    https://github.com/elixir-lang/elixir/blob/master/lib/elixir/lib/calendar.ex   https://github.com/jeremyjh/dialyxir#explanations    https://www.linkedin.com/in/travis-elnicky-4a3b2844/   https://twitter.com/_elnicky   https://twitter.com/podium_eng?lang=en   https://www.facebook.com/Elixir-Mix    https://twitter.com/elixir_mix  PicksMark Ericksen:  https://thinkingelixir.com/   Eric Oestrich:  Links Awakening   Michael Ries:  Hacktoberfest   https://nats.io/   Travis Elnicky:  Designing Elixir Systems with OTP   https://www.acquired.fm/  Special Guest: Travis Elnicky. Advertising Inquiries: https://redcircle.com/brandsPrivacy &amp; Opt-Out: https://redcircle.com/privacy

In this week’s episode of Elixir Mix the panel interviews Travis Elnicky, software architect at Podium. Podium is Utah based company that has been using Elixir for three years. Travis explains Podium’s history and its experience adopting Elixir. When Travis started at Podium they were a small startup with, he was their 16th employee. They were using Ruby on Rails and focusing on collecting reviews for local businesses. When they saw a need for a messenger application, they tried a few solutions choosing Elixir because of the familiarity they felt coming from a Rails background. After switching to Elixir, Podium grew rapidly. Now Podium has 700 employees, 130 of whom are engineers. Travis discusses with the panel how things are run over at Podium. Their teams are aligned around products and features. This makes all their engineers' full-stack developers. Podiums teams run with a lot of autonomy, they also have teams that help with internal tooling to tie the products together.The panel is curious about the recruitment process at Podium. Travis explains that their hiring is mostly based on referrals, which they found has been pretty reliable. The panel discusses the value of referrals incentives programs. By hiring referrals they save money placing ads and going to fairs. Referrals tend to be more aware of the job they are going into and already have a friend to help them transition jobs and frameworks.Next, Travis walks through what it is like for a new hire at Podium. After onboarding, the new hire sits down with their team lead and codes, taking it all the way to production. The panel considers the advantages of new hires diving in, whether or not they know Elixir. It introduces them to the work they will be doing, gives them confidence by contributing to the team, and the one on one attention shows them the culture of unity at Podium.Podium has a lot to offers its developers. It has a team whose focus is internal developer experience. Podium maintains a focus on learning and growing in Elixir. They offer training for those who are unfamiliar with Elixir. Once per week, they do a Nerd Lunch, the company buys them all lunch while Podium engineers teach their fellows about software. Elixir 101 training also happens every week and is also taught by Podium engineers. Allowing Podium engineers to teach gives learners a chance to teach which in turn helps them learn. It also allows engineers to network outside their assigned teams. The panel considers how people-centered all the solutions are at Podium. The panel wonders if Podium ever uses outside trainers or services. Travis shares the wonderful experience they have been having by using Plataformatec’s Elixir Development subscription. He says it has been incredible to be able to jump on a call, talk to them and get some feedback. Using the subscriptions allows their senior developers to level up, while the other classes and lunches helps the junior developers to level up. Podium recently sponsored ElixirConf and send a big crowd to a few different conferences every year. Travis explains the value of the conference is not only in the education received by the engineers who get to go. At Podium, the engineers who go to the conferences then come back and present what they learned at the conference, sharing what they think Podium could apply to their stack. This makes the conferences valuable to the entire team. The last topic the panel discusses in the episode is the CI at Podium. The panel explains that most of the feedback for a new developer should be coming from the CI. Travis explains how the CI is set up. When he started they were using Github and has moved to Gitlab. They use credo checks, unit tests, sobelow, and dialyzer. The panel asks about Elixir formatter and how they check format in the CI. Travis explains what he likes about credo and gives tips for running it. The panel has Travis introduces sobelow and what it does for Podium. Dialyzer is considered by the panel, they explain the trade-off of using dialyzer while sharing times that it had saved their bacon.Panelists<ul> <li> Mark Ericksen </li> <li> Eric Oestrich </li> <li> Michael Ries </li> </ul><h3>Guest</h3><ul> <li> Travis Elnicky </li> </ul><h3>Sponsors  </h3><ul> <li> <a href="http://sentry.io/" rel="nofollow" target="_blank">Sentry</a>– use the code “devchat” for two months free on Sentry’s small plan </li> <li> <a href="https://devchat.tv/sustain-our-software/" rel="nofollow" target="_blank">Sustain Our Software</a> </li> <li> <a href="https://devchat.tv/views-on-vue/" rel="nofollow" target="_blank">Views on Vue</a> </li> <li> <a href="https://www.cachefly.com/" rel="nofollow" target="_blank">CacheFly</a> </li> </ul><h3>Links</h3><ul> <li> <a href="https://medium.com/podium-engineering/two-years-of-elixir-at-podium-thoughts-9f30defedb7d" rel="nofollow" target="_blank">Two Years of Elixir at Podium: Thoughts</a> </li> <li> <a href="https://www.podium.com/" rel="nofollow" target="_blank">https://www.podium.com/</a> </li> <li> <a href="http://pages.plataformatec.com.br/elixir-development-subscription" rel="nofollow" target="_blank">http://pages.plataformatec.com.br/elixir-development-subscription</a> </li> <li> <a href="https://docs.gitlab.com/ee/ci/" rel="nofollow" target="_blank">https://docs.gitlab.com/ee/ci/</a> </li> <li> <a href="https://github.com/rrrene/credo/" rel="nofollow" target="_blank">https://github.com/rrrene/credo/</a> </li> <li> <a href="https://github.com/nccgroup/sobelow" rel="nofollow" target="_blank">https://github.com/nccgroup/sobelow</a> </li> <li> <a href="https://hex.pm/packages/dialyxir" rel="nofollow" target="_blank">https://hex.pm/packages/dialyxir</a> </li> <li> <a href="https://hexdocs.pm/mix/master/Mix.Tasks.Format.html" rel="nofollow" target="_blank">https://hexdocs.pm/mix/master/Mix.Tasks.Format.html</a> </li> <li> <a href="https://github.com/elixir-lang/elixir/blob/master/lib/elixir/lib/calendar.ex" rel="nofollow" target="_blank">https://github.com/elixir-lang/elixir/blob/master/lib/elixir/lib/calendar.ex</a> </li> <li> <a href="https://github.com/jeremyjh/dialyxir#explanations" rel="nofollow" target="_blank">https://github.com/jeremyjh/dialyxir#explanations</a> </li> <li> <a href="https://www.linkedin.com/in/travis-elnicky-4a3b2844/" rel="nofollow" target="_blank">https://www.linkedin.com/in/travis-elnicky-4a3b2844/</a> </li> <li> <a href="https://twitter.com/_elnicky" rel="nofollow" target="_blank">https://twitter.com/_elnicky</a> </li> <li> <a href="https://twitter.com/podium_eng?lang=en" rel="nofollow" target="_blank">https://twitter.com/podium_eng?lang=en</a> </li> <li> <a href="https://www.facebook.com/Elixir-Mix" rel="nofollow" target="_blank">https://www.facebook.com/Elixir-Mix</a> </li> <li> <a href="https://twitter.com/elixir_mix" rel="nofollow" target="_blank">https://twitter.com/elixir_mix</a> </li> </ul><h3>Picks</h3>Mark Ericksen:<ul> <li> <a href="https://thinkingelixir.com/" rel="nofollow" target="_blank">https://thinkingelixir.com/</a> </li> </ul>Eric Oestrich:<ul> <li> <a href="https://www.zelda.com/links-awakening/" rel="nofollow" target="_blank">Links Awakening</a> </li> </ul>Michael Ries:<ul> <li> <a href="https://hacktoberfest.digitalocean.com/" rel="nofollow" target="_blank">Hacktoberfest</a> </li> <li> <a href="https://nats.io/" rel="nofollow" target="_blank">https://nats.io/</a> </li> </ul>Travis Elnicky:<ul> <li> <a href="https://pragprog.com/book/jgotp/designing-elixir-systems-with-otp" rel="nofollow" target="_blank">Designing Elixir Systems with OTP</a> </li> <li><a href="https://www.acquired.fm/" rel="nofollow" target="_blank">https://www.acquired.fm/</a> </li> </ul>Special Guest: Travis Elnicky. Advertising Inquiries: <a href="https://redcircle.com/brands" rel="nofollow" target="_blank">https://redcircle.com/brands</a> Privacy &amp; Opt-Out: <a href="https://redcircle.com/privacy" rel="nofollow" target="_blank">https://redcircle.com/privacy</a>

EMx 072: People-Centered Solutions with Travis Elnicky

In this week’s episode of Elixir Mix the panel interviews Travis Elnicky, software architect at Podium. Podium is Utah based company that has been using Elixir for three years. Travis explains Podium’s history and its experience adopting Elixir.  When Travis started at Podium they were a small startup with, he was their 16th employee. They were using Ruby on Rails and focusing on collecting reviews for local businesses. When they saw a need for a messenger application, they tried a few solutions choosing Elixir because of the familiarity they felt coming from a Rails background. After switching to Elixir, Podium grew rapidly. Now Podium has 700 employees, 130 of whom are engineers.  Travis discusses with the panel how things are run over at Podium. Their teams are aligned around products and features. This makes all their engineers' full-stack developers. Podiums teams run with a lot of autonomy, they also have teams that help with internal tooling to tie the products together. The panel is curious about the recruitment process at Podium. Travis explains that their hiring is mostly based on referrals, which they found has been pretty reliable. The panel discusses the value of referrals incentives programs. By hiring referrals they save money placing ads and going to fairs. Referrals tend to be more aware of the job they are going into and already have a friend to help them transition jobs and frameworks. Next, Travis walks through what it is like for a new hire at Podium. After onboarding, the new hire sits down with their team lead and codes, taking it all the way to production. The panel considers the advantages of new hires diving in, whether or not they know Elixir. It introduces them to the work they will be doing, gives them confidence by contributing to the team, and the one on one attention shows them the culture of unity at Podium. Podium has a lot to offers its developers. It has a team whose focus is internal developer experience. Podium maintains a focus on learning and growing in Elixir. They offer training for those who are unfamiliar with Elixir. Once per week, they do a Nerd Lunch, the company buys them all lunch while Podium engineers teach their fellows about software.  Elixir 101 training also happens every week and is also taught by Podium engineers. Allowing Podium engineers to teach gives learners a chance to teach which in turn helps them learn. It also allows engineers to network outside their assigned teams. The panel considers how people-centered all the solutions are at Podium.  The panel wonders if Podium ever uses outside trainers or services. Travis shares the wonderful experience they have been having by using Plataformatec’s Elixir Development subscription. He says it has been incredible to be able to jump on a call, talk to them and get some feedback. Using the subscriptions allows their senior developers to level up, while the other classes and lunches helps the junior developers to level up.  Podium recently sponsored ElixirConf and send a big crowd to a few different conferences every year. Travis explains the value of the conference is not only in the education received by the engineers who get to go. At Podium, the engineers who go to the conferences then come back and present what they learned at the conference, sharing what they think Podium could apply to their stack. This makes the conferences valuable to the entire team.  The last topic the panel discusses in the episode is the CI at Podium. The panel explains that most of the feedback for a new developer should be coming from the CI. Travis explains how the CI is set up. When he started they were using Github and has moved to Gitlab. They use credo checks, unit tests, sobelow, and dialyzer.  The panel asks about Elixir formatter and how they check format in the CI. Travis explains what he likes about credo and gives tips for running it. The panel has Travis introduces sobelow and what it does for Podium. Dialyzer is considered by the panel, they explain the trade-off of using dialyzer while sharing times that it had saved their bacon. Panelists   Mark Ericksen   Eric Oestrich   Michael Ries   Guest   Travis Elnicky   Sponsors     Sentry– use the code “devchat” for two months free on Sentry’s small plan   Sustain Our Software   Views on Vue   CacheFly   Links   Two Years of Elixir at Podium: Thoughts   https://www.podium.com/    http://pages.plataformatec.com.br/elixir-development-subscription    https://docs.gitlab.com/ee/ci/    https://github.com/rrrene/credo/    https://github.com/nccgroup/sobelow    https://hex.pm/packages/dialyxir    https://hexdocs.pm/mix/master/Mix.Tasks.Format.html    https://github.com/elixir-lang/elixir/blob/master/lib/elixir/lib/calendar.ex   https://github.com/jeremyjh/dialyxir#explanations    https://www.linkedin.com/in/travis-elnicky-4a3b2844/   https://twitter.com/_elnicky   https://twitter.com/podium_eng?lang=en   https://www.facebook.com/Elixir-Mix    https://twitter.com/elixir_mix   Picks Mark Ericksen:   https://thinkingelixir.com/    Eric Oestrich:   Links Awakening    Michael Ries:   Hacktoberfest   https://nats.io/    Travis Elnicky:   Designing Elixir Systems with OTP   https://www.acquired.fm/ 

In this week’s episode of Elixir Mix the panel interviews Travis Elnicky, software architect at Podium. Podium is Utah based company that has been using Elixir for three years. Travis explains Podium’s history and its experience adopting Elixir.  When Travis started at Podium they were a small startup with, he was their 16th employee. They were using Ruby on Rails and focusing on collecting reviews for local businesses. When they saw a need for a messenger application, they tried a few solutions choosing Elixir because of the familiarity they felt coming from a Rails background. After switching to Elixir, Podium grew rapidly. Now Podium has 700 employees, 130 of whom are engineers.  Travis discusses with the panel how things are run over at Podium. Their teams are aligned around products and features. This makes all their engineers' full-stack developers. Podiums teams run with a lot of autonomy, they also have teams that help with internal tooling to tie the products together. The panel is curious about the recruitment process at Podium. Travis explains that their hiring is mostly based on referrals, which they found has been pretty reliable. The panel discusses the value of referrals incentives programs. By hiring referrals they save money placing ads and going to fairs. Referrals tend to be more aware of the job they are going into and already have a friend to help them transition jobs and frameworks. Next, Travis walks through what it is like for a new hire at Podium. After onboarding, the new hire sits down with their team lead and codes, taking it all the way to production. The panel considers the advantages of new hires diving in, whether or not they know Elixir. It introduces them to the work they will be doing, gives them confidence by contributing to the team, and the one on one attention shows them the culture of unity at Podium. Podium has a lot to offers its developers. It has a team whose focus is internal developer experience. Podium maintains a focus on learning and growing in Elixir. They offer training for those who are unfamiliar with Elixir. Once per week, they do a Nerd Lunch, the company buys them all lunch while Podium engineers teach their fellows about software.  Elixir 101 training also happens every week and is also taught by Podium engineers. Allowing Podium engineers to teach gives learners a chance to teach which in turn helps them learn. It also allows engineers to network outside their assigned teams. The panel considers how people-centered all the solutions are at Podium.  The panel wonders if Podium ever uses outside trainers or services. Travis shares the wonderful experience they have been having by using Plataformatec’s Elixir Development subscription. He says it has been incredible to be able to jump on a call, talk to them and get some feedback. Using the subscriptions allows their senior developers to level up, while the other classes and lunches helps the junior developers to level up.  Podium recently sponsored ElixirConf and send a big crowd to a few different conferences every year. Travis explains the value of the conference is not only in the education received by the engineers who get to go. At Podium, the engineers who go to the conferences then come back and present what they learned at the conference, sharing what they think Podium could apply to their stack. This makes the conferences valuable to the entire team.  The last topic the panel discusses in the episode is the CI at Podium. The panel explains that most of the feedback for a new developer should be coming from the CI. Travis explains how the CI is set up. When he started they were using Github and has moved to Gitlab. They use credo checks, unit tests, sobelow, and dialyzer.  The panel asks about Elixir formatter and how they check format in the CI. Travis explains what he likes about credo and gives tips for running it. The panel has Travis introduces sobelow and what it does for Podium. Dialyzer is considered by the panel, they explain the trade-off of using dialyzer while sharing times that it had saved their bacon. Panelists <ul> <li> Mark Ericksen </li> <li> Eric Oestrich </li> <li> Michael Ries </li> </ul> <h3>Guest</h3> <ul> <li> Travis Elnicky </li> </ul> <h3>Sponsors  </h3> <ul> <li> <a href="http://sentry.io/" rel="nofollow" target="_blank">Sentry</a>– use the code “devchat” for two months free on Sentry’s small plan </li> <li> <a href="https://devchat.tv/sustain-our-software/" rel="nofollow" target="_blank">Sustain Our Software</a> </li> <li> <a href="https://devchat.tv/views-on-vue/" rel="nofollow" target="_blank">Views on Vue</a> </li> <li> <a href="https://www.cachefly.com/" rel="nofollow" target="_blank">CacheFly</a> </li> </ul> <h3>Links</h3> <ul> <li> <a href="https://medium.com/podium-engineering/two-years-of-elixir-at-podium-thoughts-9f30defedb7d" rel="nofollow" target="_blank">Two Years of Elixir at Podium: Thoughts</a> </li> <li> <a href="https://www.podium.com/" rel="nofollow" target="_blank">https://www.podium.com/</a> </li> <li> <a href="http://pages.plataformatec.com.br/elixir-development-subscription" rel="nofollow" target="_blank">http://pages.plataformatec.com.br/elixir-development-subscription</a> </li> <li> <a href="https://docs.gitlab.com/ee/ci/" rel="nofollow" target="_blank">https://docs.gitlab.com/ee/ci/</a> </li> <li> <a href="https://github.com/rrrene/credo/" rel="nofollow" target="_blank">https://github.com/rrrene/credo/</a> </li> <li> <a href="https://github.com/nccgroup/sobelow" rel="nofollow" target="_blank">https://github.com/nccgroup/sobelow</a> </li> <li> <a href="https://hex.pm/packages/dialyxir" rel="nofollow" target="_blank">https://hex.pm/packages/dialyxir</a> </li> <li> <a href="https://hexdocs.pm/mix/master/Mix.Tasks.Format.html" rel="nofollow" target="_blank">https://hexdocs.pm/mix/master/Mix.Tasks.Format.html</a> </li> <li> <a href="https://github.com/elixir-lang/elixir/blob/master/lib/elixir/lib/calendar.ex" rel="nofollow" target="_blank">https://github.com/elixir-lang/elixir/blob/master/lib/elixir/lib/calendar.ex</a> </li> <li> <a href="https://github.com/jeremyjh/dialyxir#explanations" rel="nofollow" target="_blank">https://github.com/jeremyjh/dialyxir#explanations</a> </li> <li> <a href="https://www.linkedin.com/in/travis-elnicky-4a3b2844/" rel="nofollow" target="_blank">https://www.linkedin.com/in/travis-elnicky-4a3b2844/</a> </li> <li> <a href="https://twitter.com/_elnicky" rel="nofollow" target="_blank">https://twitter.com/_elnicky</a> </li> <li> <a href="https://twitter.com/podium_eng?lang=en" rel="nofollow" target="_blank">https://twitter.com/podium_eng?lang=en</a> </li> <li> <a href="https://www.facebook.com/Elixir-Mix" rel="nofollow" target="_blank">https://www.facebook.com/Elixir-Mix</a> </li> <li> <a href="https://twitter.com/elixir_mix" rel="nofollow" target="_blank">https://twitter.com/elixir_mix</a> </li> </ul> <h3>Picks</h3> Mark Ericksen: <ul> <li> <a href="https://thinkingelixir.com/" rel="nofollow" target="_blank">https://thinkingelixir.com/</a> </li> </ul> Eric Oestrich: <ul> <li> <a href="https://www.zelda.com/links-awakening/" rel="nofollow" target="_blank">Links Awakening</a> </li> </ul> Michael Ries: <ul> <li> <a href="https://hacktoberfest.digitalocean.com/" rel="nofollow" target="_blank">Hacktoberfest</a> </li> <li> <a href="https://nats.io/" rel="nofollow" target="_blank">https://nats.io/</a> </li> </ul> Travis Elnicky: <ul> <li> <a href="https://pragprog.com/book/jgotp/designing-elixir-systems-with-otp" rel="nofollow" target="_blank">Designing Elixir Systems with OTP</a> </li> <li><a href="https://www.acquired.fm/" rel="nofollow" target="_blank">https://www.acquired.fm/</a> </li></ul>