Bob Lee presents persistence queues, the technology stack, the publish-subscribe pattern and dependency injection as used by Square.com.
Blake Matheny discusses the current status of Tumblr, its evolution and lessons learned along the way, 3 types of concurrency -Macro, Mecro and Micro-, and Motherboy –a dashboard system-.
Jeremy Jarvis shares his experience building a IaaS cloud and some of the lessons learned along the way.
Andy Britcliffe shares some lessons learned building software for the cloud, along with advice on architecture, technologies and the need for vendor support.
Ingo Rammer shares 15 tips regarding people, complexity and technology that he learned doing software architecture for 15 years.
Ola Bini discusses using open source in distributed teams from a sociological, political, and organizational point of view, providing some lessons useful in daily development.
Jesper Boeg shares his experience, lessons learned, failures, and common problems met when introducing Kanban to various teams having no previous Agile or Lean experience
Eoin Woods shares some of his architectural experience along with principles and techniques useful when working with legacy systems.
David Dawson and Marcus Kern share lessons learned creating a high-performance mass audience participation system using NoSQL.
Graham Tackley shares the lessons learned running The Guardian website on Java, and why they decided to switch to Scala and how it helps them.
Jeremy Edberg shares the need, the benefits, the pain points and the lessons learned moving Reddit and Netflix’s internal solution to Amazon AWS.
Rob Bowley shares lessons learned while doing Agile: Scrum is not that bad, Don’t call it Agile, Doing the right thing vs doing it right, Identify the change agents, Hire good people, etc.