Joe Armstrong
Inventor of Erlang
Ericsson AB
Joe Armstrong is one of the three inventors of Erlang. When at the Ericsson computer science lab in 1986, he was part of the team who designed and implemented the first version of Erlang. He has written several Erlang books including Programming Erlang Software for a Concurrent World. Joe held the first ever Erlang course, taught Erlang to hundreds of programmers and held many lectures and keynotes describing the technology.
Joe has a PhD in computer science from the Royal Institute of Technology in Stockholm, Sweden and he is an expert in the construction of fault tolerant systems. Joe was the chief software architect of the project which produced the Erlang OTP system. He has worked as an entrepreneur in one of the first Erlang startups (Bluetail) and has worked for 30 years in industry and research.
Favourite quote: "... or music heard so deeply That it is not heard at all, but you are the music While the music lasts."
Joe's book
Joe has a PhD in computer science from the Royal Institute of Technology in Stockholm, Sweden and he is an expert in the construction of fault tolerant systems. Joe was the chief software architect of the project which produced the Erlang OTP system. He has worked as an entrepreneur in one of the first Erlang startups (Bluetail) and has worked for 30 years in industry and research.
Favourite quote: "... or music heard so deeply That it is not heard at all, but you are the music While the music lasts."
Joe's book
twitter: @joeerl
Joe Armstrong is Giving the Following Talks
OTP Rationale
What is OTP and why was it created?
OTP is a number of different things:
- A delivery platform for Erlang and the Erlang VM
- A large set of general purpose libraries
- A set of design patterns
- A set of design documents
- A way of working
OTP was designed to meet the demands of large organisations. It was the third rewrite of a set of libraries and procedures used to develop complex Telecoms applications.
This talk delves into the history of OTP and tries to explain the rationale behind OTP.