Panelists answer questions on the languages they contributed to: How do you organize thoughts and code? What unique advances in usability did your language make? Why do your users love to code in it?
Kenji Rikitake discusses using Erlang/OTP for IoT, covering communication protocols, design principles and overcoming hardware limitations for endpoint devices in fault-tolerant systems.
Kostis Sagonas introduces the idea of concolic unit testing of Erlang programs and the CutEr tool, how it is different, and how it can be used to identify errors in programs in a fully automatic way.
Jamshid Mahdavi explains how WhatsApp has developed their server components, the deployment processes, and how they monitor, alert, and repair the inevitable failures in a billion-users service.
Jordan Day introduces the Elixir language, its syntax and the semantics of an Elixir application, highlighting differences that make Elixir apps more reliable than those written in other languages.
Irina Guberman discusses maximizing throughput on multicore systems with Erlang and the Jobs framework by Ulf Wiger.
Joseph Blomstedt presents ongoing work to build a new set of high performance data structures for Erlang, including both single process data structures as well as various concurrent data structures.
Ransom Richardson presents the Talko service architecture, its implementation and operation in the cloud, why they are using Erlang for it and key things learned along the way.
Garrett Smith outlines a methodology for pattern discovery and presents a number of specific patterns that Erlang programmers can use to build programs that feel alive.
Simon Thompson shows how Wrangler can help with making systems run on multi-core hardware, including three Wrangler refactoring techniques for retrofitting concurrency to Erlang applications.
Daniel Pezely discusses the 10 fold performance increase of a Lisp and C system after rewriting it in Erlang, outlining where issues existed before and the design and implementation of the new system.
Christopher Meiklejohn looks at applying two techniques together, deterministic data flow programming and conflict-free replicated data types, to create highly available and fault-tolerant systems.