Alasdair Allan discusses the security problems when building Internet of Things devices, and the underlying differences between the IoT and the digital Internet that drive those security issues.
Michelle Brush discusses modeling complex systems and architectural changes that could introduce new modes of failure, using examples from embedded systems to large stream processing pipelines.
Ali Basiri discusses the motivation behind ChAP (Chaos Automation Platform), how they implemented it, and how Netflix service teams are using it to identify systemic weaknesses.
Amber Case discusses using Calm Technology to design the next generation of connected devices, covering notification styles, compressing information into other senses, and cognitive overhead.
Kavya Joshi discusses the internals of the Go race detector and delves into the compiler instrumentation of the program, and the runtime module that detects data races.
Dmitry Ivanov discusses the basic CRDTs implementations in Scala, explaining the advantages of these data structures to solve many synchronization problems as well as their limitations.
Jim Plush discusses specific culture initiatives, team structures and management ideals that have worked for his team at CrowdStrike, their virtual team structure, the culture team and more.
Kolton Andrus and Peter Alvaro present how a “big idea” -- lineage-driven fault injection -- evolved from a theoretical model into an automated failure testing service at Netflix.
Avi Kivity discusses ScyllaDB, the many necessary design decisions, from the programming language and programming model through low-level details and up to the advanced cache design, and more.
Devon H O'Dell discusses how perceptions about one's own abilities influence goals and behaviors, and how to improve abilities and help others do the same starting with a simple shift in thinking.
Sara Bayless da Costa discusses several prototyping methods helping to learn about product, gather quality feedback, and get the best version of a product out there as quickly as possible.
Phil Haack discusses the secret ingredient to great teams and products, usually misnamed "soft" skills, and how they help teams be more effective, backing all of it with hard data.