Engineering Elixir Applications: If you don't deploy it, it ain't real

[ElixirConf]

Engineering Elixir Applications: If you don’t deploy it, it ain’t real.

Engineering Elixir Applications: If you don't deploy it, it ain't real.

ElixirConf US 2024 Ellie Fairholm & Josep (Pep) Giralt D’Lacoste

Welcome to ElixirConf
Welcome to ElixirConf

The phrase “DevOps” sparks the idea of an intersection between dev and ops teams - like the centre of a Venn diagram. But decision fatigue and the perceived complexity of the operations world have often caused these teams to drift apart. Rather than becoming more cohesive, “dev” and “ops” teams are becoming increasingly siloed.

We propose that empowering developers to understand and participate in the deployment of software will lead to happier and healthier teams. Knowing how to write efficient application software will only get you so far. We’d like to empower you to leave the comfort of your FE, BE or ops zone and jump over the fence to learn how the others do it.

BEAM technologies are fault tolerant and reliable by design, and you and your development teams should be the same. Environment integrity, infrastructure-as-code, Phoenix LiveView and CI/CD should be things that all of your team understand and excel in. Having knowledge of all parts of the software delivery process means that you’ll be able to share responsibilities and work together more efficiently. Team members should be able to seamlessly cover for one another, ensuring continuous operation (just like a BEAM process).

Only then can you and your team thrive; not only in the work that you do, but also the way you do it. Knowledge should be shared rather than kept under lock and key. We’ll talk about the principles that efficient teams should embody and how encouraging developers to understand deployment will improve performance and happiness. Because in the end, if you don’t deploy it, it ain’t real.

Comments welcome! View the elixirconf tag for more ElixirConf talks!

[ragamuf]

Very welcomed conversation to have as a developer myself. The division hurts creativity and productivity as some problems are more easily solved in the deployment pipeline. Thus it helps to be able to weigh both pathways when accessing solutions.