Thomas Herrmann discusses the advantages, challenges and lessons learned in building a multimedia-heavy, interactive HTML5 application with Ember.js.
Zach Holman discusses the various stumbling blocks GitHub encountered as the company grew over the years.
Ed Cortis shares lessons learned adopting ABW, covering the pilot program, noise/quiet spaces, tools, curtains, card walls, people, logistics, etc.
Alan Griffiths shares the organizational process, the technological challenges and the solutions adopted by a team developing a C++ systems component.
Marton Anka shares lessons learned and technical details scaling LogMeIn over a decade.
Jesper Richter-Reichhelm shares lessons learned from failures while scaling Wooga games to millions of daily users.
Volker Pacher explains why Shutl chose Neo4j when faced with the need of building a new API meant to support business growth, the challenges met during implementation and solutions applied.
Jon Tirsen and Douwe Osinga tell Triposo’s story from a small hobby project to the large architecture of today. Triposo is a mobile phone travel guide.
Trevor Lalish-Menagh shares his experience introducing Kanban, what has worked and what hasn’t.
Marc Pacheco tells how Songkick made radical changes to increase the performance of the site while retaining a productive development team.
Andrew Godwin tells Lanyrd’s story, covering the technology stack, tricks used, and what they would do differently if they could start afresh.
Steve Smith shares some of the change patterns used to establish the Continuous Delivery of 60+ applications at Sky Network Services over the past 2 years, and how they fit into an optimal cycle time strategy.