[erlang-questions] Erlang for managers
Fri Feb 26 09:39:57 CET 2016
You can have a look at a slide deck I created at one point:
The Golden Trinity of Erlang (s.24) is the key.
Fred has given a good explanation of the Zen of Erlang:
I think the "Building Microservices" by Sam Newman
has a very favourable mentioning of Erlang's ability to deliver on
If you are a pure Erlang shop, the quality of Erlang's module
implementation may get you a very long way, but I suspect that many of
you are not in that situation.
For me one of the key business values of Erlang is that if you have done
your supervision tree well, then you can add new services to your system
without worrying. If you have created something that fails, the only
that part fails. The rest of your system continues.
This significantly reduces the risk of adding to your system.
You have to learn how to split things into smaller pieces, but that is a
sane advice in any language.
jlouis has some good remarks on this in
So smaller, indenpendent components that can fail on their own leads to
a higher innovation rate, which leads to money.
You can code just as fast in a lot of other languages, but the freedom
to make mistakes that Erlang lends you is worth so much more.
Feel free to reach out if you need a discussion about this.
Martin Hässler <mhssler@REDACTED> writes:
> [ text/plain ]
> My manager's new manager has asked me for a high level summary of Erlang
> compared with other languages, especially C and C++, an "Erlang for dummies"
> as she put it. I would like to call it "Erlang for managers" instead, as she
> is not a dummy.
> What are the best Erlang summaries for managers nowadays?
> erlang-questions mailing list
M: +45 25 14 05 38
More information about the erlang-questions