Nat Pryce exemplifies how he dealt with flickering, false positives, slow, and messy tests appearing in asynchronous testing when trying to perform end-to-end testing.
Simon Baker and Gus Power point out that many projects fail due to organizational complexity, proposing ways to improve product development and business agility in order to make the customer happy.
Udi Dahan addresses SOA from both a technological and business perspective by introducing business and autonomous components, basic elements of a service-oriented solution for the enterprise.
Russ Miles and Toby Hobson outline many factors to be considered when adopting a cloud solution, creating a wider view of the cloud from the development and business perspective.
Alex Blewitt, Kevin Seal and Alex Buckley answer Java modularity-related questions: when is modularity needed, how to address it, and what are the improvements in OSGi-based development.
Adam Blum discusses the current trends in mobile development and smartphones, trying to predict what will happen in this area over the next 5 years so a developer would know what to expect.
Roy Osherove discusses the difficulties met when trying to test code embedded in a framework (cog), presenting several solutions to create unit tests for cogs, using Silverlight code as example.
Ross Mason discusses how to use enterprise mashups by applying a number of patterns, such as FeedFactory, Super Search, and Pipeline, in order to find new ways to benefit from existing enterprise data
Udi Dahan discusses the Command Query Responsibility Segregation (CQRS) pattern, detailing on queries and commands, what they are and how they should be used in an asynchronous programming environment
Ralph Johnson discusses principles, practices and tools relating to software development starting from already existing code which needs refactoring, maintenance, and sometimes architectural change.
Pete Goodliffe provokes his listeners to keep learning, offering advice on how to approach learning, what is valuable and what can be ignored, how to deal with new things, having a healthy attitude.
Mark Ramm talks on why they chose MongoDB for SourceForge, how it compared to other possible solutions, the problems encountered, how they fixed them, overall lessons learned, and answering questions.