List of videos

In this talk Erik and Tobias will present a new blockchain built in Erlang and Elixir to run on top of the BEAM. They will give a brief introduction to blockchain technology and then present the AEternity project and some of its features, such as State Channels and Oracles. They will also talk about the execution of smart contracts on the blockchain, the whys and hows. The AEternity smart contracts can be written in a functional programming language. They will conclude by explaining how it is currently implemented and some of the highlights they have plan for smart contracts in the future. More details on website: https://codesync.global/speaker/erik-stenman/

Andrew will present a talk on a new open source package - Sage, explaining what use cases it covers. He will also discuss approaches for dealing with distributed transactions generally. More details on website: https://codesync.global/speaker/andrew-dryga/

As it turns out, Erlang or Elixir aren't the fastest kid on the block. And while raw CPU speed matters little for most applications, there does exist a couple reasons you might want want to reach for tools that give you access to native power. In this talk we will discuss Native Implemented Functions (NIFs) - Erlang's Foreign Function Interface (FFI). NIFs are normally implemented in C and are considered dangerous. But we're going to explore writing safer NIFs in Rust - a new systems programming language developed by Mozilla, that focuses on memory safety. We'll talk about the pitfalls with writing NIFs and how Rust can make this process easier and safer. More details on website: https://codesync.global/speaker/sonny-scroggin/

The main goal with "logger" is to standardise an API for logging, allowing the application implementer to use this API without making any assumptions about the logging backend that will be used in the final system. That is, we want to remove the dependency, between applications and logging facility. The main goal is not to remove the need for good logging applications like Lager, but to lift the decision about logging from the low level application implementer to the high level system architect. This will also make it easier to combine applications from different providers - since the same API is always used. Thus, individual applications don't need a dependency to a logging backend such as Lager. That dependency is decided on system level instead. We want a built-in logging feature which is "good" by default, but which can be customized and extended if needed. The talk will tell you how it works and explain the design decisions. More details on website: https://codesync.global/speaker/kenneth-lundin/

OBJECTIVES One person in the audience decides to test their startup idea, and another decides not to.

Erlang/OTP was released Open Source 20 years ago. This talk is about the Open Source journey and how it has impacted, and still impacts, the Erlang/OTP teams way of working. How do we balance propriety interests of Ericsson with the interests of the Open Source community? Why Open Source is important for the existence of Erlang/OTP! How Open Source contributes to making Erlang/OTP great! More details on website: https://codesync.global/conferences/code-beam-sto-2018/

Twenty years after the Open Source Initiative was created, open source has grown from a disruptive idea to a default approach to software. This talk will review the first twenty years of open source and suggest some trends for the next ten. More details on website: https://codesync.global/speaker/simon-phipps/

Raxx can be used to build web applications much like Plug. However that is where the similarities end. Raxx aims to simplify web applications by promoting simple concepts like functional purity and message passing. I started the project in 2016. Since then, it has matured to the point where it has been used in several production services. This talk will cover an introduction to the project; an overview of the rationale behind it, and finally a vision of what comes next. More details here: https://codesync.global/speaker/peter-saxton/

Testing is a major part of all software development - yet no matter how much effort is spent on it, some errors always seem to slip through. Cases which "no-one thought to test" crash systems late in development or out in the field, revealing errors which cost time and money to analyze, diagnose, and fix. In the worst case, such errors reveal fundamental flaws which force a redesign of part of the system, at disproportionate cost. QuickCheck is an automated testing tool addressing the testing challenges by automatically generating test cases from a concise specification (so that many more cases can be tested), and simplifying failing cases to a minimal example on a test failure (so that fault diagnosis is quick and easy). QuickCheck enables developers to generate tests from specifications. It enables them to find errors at an earlier stage, lowering costs and improving quality as a result. In this tutorial, Thomas Arts will use examples to show how developers write QuickCheck specifications - which are actually Erlang programs using the QuickCheck API - and use them to test code written in Erlang or other programming languages. We will see how QuickCheck's shrinking finds tiny examples that provoke errors, making the step from observing a bug to diagnosing it very short indeed. More details here: https://codesync.global/speaker/thomas-arts/