David Harrison presents the API and culture journey at freelancer.com.
Jon Moore goes over some strategies for surviving in a jungle of partial failures. Each survival tip is explained through a concrete example, or "adventure story", from Comcast’s TV experience.
John Housego describes how W. L. Gore & Associates manages to maintain a global corporation without hierarchies, that keeps the bureaucracy as small as possible.
Nathan Peterson introduces Behavior Driven Development, showcasing its adoption by his team along with successes and failures using it.
Mark O’Neill presents a number of real-life case studies about how businesses worldwide are succeeding with APIs, enabling new business channels and revenue.
Giannakakis and Dalkitsis present how Shazam releases faster, more predictably and with more features by using BDD and automation testing, without slowing down or hindering the development process.
Phil Calcado shares the toolkit and strategy SoundCloud uses to keep its microservices explosion manageable, dealing with operations overhead, DevOps, breaking changes and asynchronous behaviors.
Paul Glavich discusses design decisions to be made when building a new API regarding versioning, hypermedia usage, authentication and other aspects.
Stuart Williams shares from experience how his company implemented Kanban, what worked for them in handling maintenance, support and a number of small projects.
Aaron Quint shares an honest story of a team's journey, taken from his experience as CTO of Paperless Post, an organization which went from 5 to over 100 people and from a dev team of 2 to 40.
Guy Davidson, Tom Miles discuss 64-bit programming pitfalls, Unity builds, writing portable code, and persuading a large development team of varying levels of skill to write portable code as well.
Niklas Gustavsson presents Spotify's 2-layer services, and how the UNIX philosophy of composing components that does a single thing well works on a greater scale.