Mike Beltzner describes the tools and techniques used to keep Pinterest's platform stable and responsive. Garrett Moon dives into the technology they developed.
Marius Eriksen explains Twitter's experiences with functional programming (with Scala) @ Twitter: where functional techniques worked and where not. Also: how the Scala language has scaled with Twitter
The authors discuss property based testing from the basics to advanced techniques (custom data generators, performance tests, basing data generation on samples from production data,...).
Jafar Husain shows the Reactive Extensions (Rx) library which allows to treat events as collections, how Netflix uses Rx on the client and the server, allowing to build end-to-end reactive systems.
Logan Linn explores the design and implications of an architecture built around immutable data structures using ClojureScript and Om, a ClojureScript interface to Facebook's React.
Aaron Gardner pulls back the covers on the Etsy Search ecosystem and how they got here -- the good, the bad, and the funky.
Leslie Lamport makes the case for separating the design details of what a program should do and how it should work from the business of writing code, and discusses how the design process should work.
Sid Anand discusses the architectural and development practices adopted by LinkedIn as a continuous growing company.
This talk goes over the design motivation for Zen and describe its internals including the API, type system and HBase backend.
John Bunting talks about different services Tumblr has built and how their architecture helps them be fault tolerant as they continue to grow.
Andy Vaughn gives attendees a case study of how changing the development model and release cycle of a 5 year old software product to continuous delivery greatly improved the product.