Jez Humble discusses how to deal with risk management, regulation compliance, ITIL, audit requirements in a large organization that intends to adopt devops.
Eoin Woods suggests creating the architecture of a system by discovering the interactions between the components and focusing on the boundaries, helping with defining the interfaces and interactions.
Simon Brown discusses the role of the software architect, challenging some of the current assumptions and trying to redefine it in the context of Agile development.
Maximiliano Firtman discusses HTML5, the features it introduces, how it can be used for cross-platform mobile development, compatibility issues, creating apps for a store, taking a look at the future.
Michael Nygard outlines 8 rules for dealing with complex systems: Embrace Plurality, Contextualize Downstream, Beware Grandiosity, Decentralize, Isolate Failure Domains, Data Outlives Applications ...
Dragos Manolescu introduces some of the new features in Windows Phone Mango - TCP and UDP sockets, network preferences and local storage –, discussing their optimization for lower power consumption.
Eberhard Wolff introduces Cloud Computing, IaaS/PaaS, comparing the Java support provided by Google GAE, Amazon Beanstalk, VMware Cloud Foundry, and Cloud Bees.
Frank Buschmann’s secrets: User Tasks-based Design, Be Minimalist, Ensure Visibility of Domain Concepts, Use Uncertainty as a Driver, Design Between Things, Check Assumptions, Eat Your Own Dog Food.
Graham Tackley discusses how The Guardian switched all new development from Java to Scala, why they did that, what were the benefits and the problems, and why they did not choose Python+Django.
Ola Bini discusses what features a long lasting platform should have, and takes a look at Java to see if it can be that platform.
Lúcio Ferrão talks about making the software appealing to the business by using a visual language and an integrated environment supporting the entire life cycle of application development.
Dierk König introduces GPars, Groovy’s library for concurrent programming, explaining a simpler and less error-prone way to use fork/join, map/reduce, actors, and dataflow in Java and Groovy.