Mike Amundsen reviews patterns in developer practices and trends in services and libraries that emphasize the idea that in the end "Clients Matter, Services Don't".
Patrick Smacchia shares code analysis-related practices -structuring code, measuring code quality, automated tests, code contracts, reporting progress, trending- based on his experience with NDepend.
David Tanzer takes a look at the current status of software development and suggests what a team can do to stay competitive, and what a developer can do so his/her employers still need him over time.
Steve Rogalsky overviews some of the topics discussed at Agile conferences, uncovering what teams around the world are struggling or experimenting with.
Michael Nuciforo covers the recent history of mobile banking from SMS alerts to Java, then Web and Native apps. It highlights the major trends, key industry players, and consumer expectations.
Jaime Ryan discusses the rise of the Internet Service Bus based on the current global trends and requirements, making an analogy with the birth and evolution of the ESB.
Ross Mason explains what real-time API is, the corresponding technologies and trends, demoing using streaming APIs.
Aryeh Selekman discusses current trends in the mobile space, some of the technologies useful to integrate Facebook functionality into mobile applications and the latest W3C mobile standards under dev.
Martin Fowler and Rebecca Parsons discuss how data has changed over the years, what is IT’s response to this change, and how data is used by organizations these days.
Jürgen Höller reviews the major elements of Spring 3.1 and takes a peak into upcoming features in Spring 3.2 such as multi-core concurrent programming support for Java SE 7.
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.
Kent Beck shows the synergies between business and Agile development. The reason Agile is becoming more popular every day is because it responds to the business needs as they evolve.