Buckle up your shoes and prepare to tackle the unique challenge of migrating web applications to Elixir.

Become an Elixir Professional

Elixir is a relatively new framework but has shown rapid growth due to its flexibility as a functional, concurrent, distributed programming language. In this module, we'll learn about adopting an Elixir-based technology stack for distributed web applications. Then, we'll learn high-level concepts such as staffing, code management, and legacy systems. We’ll also learn to develop our Elixir environment with a walkthrough of making a functional transition, distributing Elixir, and integrating external code. We'll wrap up the module by looking at deployment and maintenance functions, assessing performance, and finalizing the application.

Adopting Elixir for Software Engineering Leads & Managers

## Need for coding standards
Every programming language has built-in idioms and practices that collectively shape the look and feel of a codebase’s structure and contents. That’s coding style. Good style is especially important to adoption because it reduces friction between developers and makes a collective codebase easier to read.

As we can imagine, some tools can help us manage many of these elements automatically. Such tools are typically divided into two categories:

1. **Code formatters** focus on code layout concerns, such as indentation, use
of spaces and newlines, line length, and the like.

2. **Linters** focus on code quality and code structure concerns that go beyond layouts, such as function and variable names.

The Elixir community embraced linters years ago but formatters are a more recent addition. Let’s start with them.

## Code formatters

You and your teams have probably already had one or more heated discussions about code style. Should we use tabs or spaces? Should we add spaces after commas or not? To mature, all new language communities must go through these discussions at some point.

Even when teams are in perfect agreement and choose a style guide that already exists in the community, enforcing such guidelines requires constant effort during development as well as code reviews. To make matters worse, as a company grows, each new developer needs to get acquainted with the house rules, and that may take some time to get used to.


# Need for coding standards
Every programming language has built-in idioms and practices that collectively shape the look and feel of a codebase’s structure and contents. That’s coding style. Good style is especially important to adoption because it reduces friction between developers and makes a collective codebase easier to read.

As we can imagine, some tools can help us manage many of these elements automatically. Such tools are typically divided into two categories:

1. **Code formatters** focus on code layout concerns, such as indentation, use
of spaces and newlines, line length, and the like.

2. **Linters** focus on code quality and code structure concerns that go beyond layouts, such as function and variable names.

The Elixir community embraced linters years ago but formatters are a more recent addition. Let’s start with them.

# Code formatters

You and your teams have probably already had one or more heated discussions about code style. Should we use tabs or spaces? Should we add spaces after commas or not? To mature, all new language communities must go through these discussions at some point.

Even when teams are in perfect agreement and choose a style guide that already exists in the community, enforcing such guidelines requires constant effort during development as well as code reviews. To make matters worse, as a company grows, each new developer needs to get acquainted with the house rules, and that may take some time to get used to.


Learn and practice code standards and code formatters in this lesson.

Three Adoption Stories

Concept: Team Building

Concept: Ensuring Code Consistency

Concept: Legacy Systems and Dependencies

Development: Making the Functional Transition

Development - Distributed Elixir

Development - Integrating with External Code

Production - Coordinating Deployments

Production - Metrics and Performance Expectations

Production - Making Your App Production Ready

Appendix

Conclusion

Coding Standards and Code Formatters

Need for coding standards