Darach Ennis talks about the actor-model language Pony, its distinguishing approaches to memory management and concurrency, how it relates to Erlang, and much more.
Adam Wick talks about software security, research into formal methods and randomisation as well as documentation and types to help write secure software, HalVM and other Unikernels, DRM.
Sylvan Clebsch introduces Pony, a language built on the actor model which combines new approaches to garbage collection and concepts like capabilities to write high performance, concurrent code.
Rick Hudson talks to Charles Humble about the evolution of Go’s garbage collector, comparing 1.5 to the forthcoming 1.6 release, and also touching on plans for 1.7.
Bryan Cantrill explains Triton (a way to run secure Linux containers on bare metal), the history of DTrace and ZFS and their (lack of) adoption on Linux, the relevance of OS R&D, Unikernels and more.
Felienne Hermans explains the how and why of applying software engineering methods (testing, static analysis, refactoring) to spreadsheets.
Chad Wathington and Suzie Prince spoke about the importance of feedback and collaboration in teams and keeping feedback going when scaling agile beyond single teams into larger organisations. Designing feedback into the process and keeping the processes people centric. They also discussed new capabilities coming in Mingle.
Mik Kersten talks about current and future trends in ALM and the support for approaches like large scale Agile, DevOps, Docker, Big Data, functional languages and the Internet of Things.
Chris Richardson explains the appeal of Scala, functional programming in Java and other languages, the basics of Event Sourcing, and his perspective on the state of the Java ecosystem.
Microservices have been a trending topic for some time now and while we talked a lot about concepts in the past there are more and more real-life experiences to draw on now. In this interview, Michael Bryzek, co-founder and former CTO of Gilt, shares some of his experience working with microservices including how we should design our architectures and APIs to avoid ending up in a dependency hell.
Tom Limoncelli explains the reasons for DevOps, how to choose which steps to automate and which not, enabling continuous deployment, and much more.
Kolton Andrus is working as "chaos engineer" at Netflix which means he is getting paid for breaking things in production. We are talking with about how to improve overall system quality by injecting failures in production systems, about the idea of "anti-fragility" in the context of software and about how engineering teams of all layers can benefit from a failure injection infrastructure.