Dan North talks about the tendency of developers-becoming-architects to create complex systems. He argues for simplicity and offers strategies to extract the simple essence from complex situations.
Kevlin Henney proposes a new look at design patterns from the perspective of the habitability of code, communication, exploration, empiricism, reasoning, incremental development, and design sharing.
Ian Robinson: the web is counterintuitive because clients are interested only in URIs and they are responsible for requests’ sequence, and one should use protocol resources , not domain resources.
Aino Vonge Corry reviews a number of well known design patterns showing that their implementation is simpler in functional languages because such languages have pattern-based constructs.
Don Syme on functional languages features, showing why and when they are useful for parallel programming: simplicity, composability, immutability, lightweight reaction, translations, data parallelism.
Bill Burke shows how to use REST to create interfaces to middleware services – messaging, transactions, workflow, security – in order to have RESTful enterprise SOA implementations.
David Harvey explores the possible danger he sees in the current Software Craftsmanship discourse which can end up creating a barrier between the software builders and their customers.
Rebecca Parsons makes an basic introduction to functional languages, explaining how to think in a functional language, why is there renewed interested in them, and some nifty things about them.
Corey Haines believes that craftsmanship means forming quality software developers who choose their own practices and use them, starting as apprentices, becoming journeymen, and ending coding katas.
Jason Gorman presents how developers can learn TDD to the point of transforming the knowledge acquired into habits by exercising a number of practices followed by peer evaluation.
Jesper Boeg talks on the origins of Kanban, software Kanban, how it is different from other Agile methods and what it is useful for, the team maturity needed, and some of disadvantages of using Kanban
Alois Reitbauer shows how to do performance testing during development, testing, and production by starting early in the development phase, breaking the test into pieces, and testing continuously.