Brujo Benavides

So you just joined a massive project with tons of poorly-maintained Erlang code. DON'T PANIC! This talk will give you many tools and techniques that you will need to start working on it confidently and productively.
You will learn multiple tips and tricks to incrementally start using the compiler, Common Test, Xref, Dialyzer, Elvis, Hank, the Formatter, and others in large codebases. A task that's generally hard to do but usually produces enormous benefits in terms of maintenance. These tools and techniques will increase your confidence, and they'll help you and your team work more efficiently.

OBJECTIVES
The goal of the task is to reduce the pain developers feel when faced with large poorly-maintained projects written in Erlang, by showing how the tools that they would use from day 0 on new projects can be introduced gradually even when they were never used before.

AUDIENCE
Almost any Erlang developer, maybe except for those who had worked with me in the past:)

This session will host an all spanish-speaking panel to talk about the BEAM; how the platform is currently used and what the future holds for anyone invested in it. Note that this panel will be delivered 98% in spanish.

Esta sesión tendrá como invitados a destacados miembros de la comunidad hispanohablante para discutir sobre BEAM; cómo es que aprovechamos la plataforma al día de hoy y qué es lo que el futuro aguarda para todos los interesados en ella. Manejaremos español durante gran parte de la sesión para la comunidad.

Working with legacy code can be very frightening sometimes. That's why most of us tend to touch as little as possible every time we need to make a change, particularly when we're removing stuff. That leads to lots and lots of "dead code" (pieces of code that are no longer needed but never removed… just in case). That piling of dead code makes debugging and maintaining systems harder and harder, and the cycle starts again…

That's why, at NextRoll, we created Hank, the Dead Code Killer.

Our latest open-source tool that you need to start using today!

OBJECTIVES:

To help developers lose the fear to delete code from large systems using Hank to help them.

AUDIENCE:

Erlang developers.

One of the first things every newcomer faces when they meet OTP are behaviours. The general explanation for them is usually along the lines of "they're like interfaces for OOP". While that's somewhat accurate, it's also misleading and introduces a lot of confusion on how and when to use the existing behaviours and when it's reasonable to define your own ones. In this talk, Brujo will explain what behaviours are, how they should be used and how to create and expose new ones if you ever need to.

OBJECTIVES

To help newcomers get familiar with OTP behaviours and to help experienced devs rediscover them.

TARGET AUDIENCE

Developers willing to understand what they really do when they implement a generic server or a supervisor. Also folks considering the creation of their own behaviours with the desire to do it right. If you don't know what a behaviour is at all, you're welcome here too.