InfoQ Homepage Agile Content on InfoQ
-
Continuous Testing in Clojure
Bill Caputo discusses adopting continuous testing for Clojure, what are the goals of such a practice, how it differs from other languages, practical considerations (tools, setup) and a demonstration.
-
15 Lessons from 15 Years as a Software Architect
Ingo Rammer shares 15 tips regarding people, complexity and technology that he learned doing software architecture for 15 years.
-
Anarchy, Cooperation and the Bazaar
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.
-
Beauty is in The Eye of the Beholder
Alex Papadimoulis attempts to define ugly code, how one can recognize it, providing advice on avoiding writing such code and refactoring old code to get rid of it.
-
Creativity, Energy, Imagination and The Business Value of Joy!
Richard Sheridan presents tools and techniques for creating an intentional culture of joy lacking fear and ambiguity, the most productive environment in his opinion.
-
Launching Kanban Teams
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
-
Co-Making Great Products
Jeff Patton presents a work style where everyone takes ownership of products, being involved in identifying and solving problems, and shares practices for collaboratively designing solutions.
-
A Team, A System, Some Legacy ... and You
Eoin Woods shares some of his architectural experience along with principles and techniques useful when working with legacy systems.
-
Ain’t No Cure for the Distributed Blues
Dan North shares his experience in a new endeavor working for a trading company with distributed teams embracing ideas from Lean and Theory of Constraints.
-
Working with MIG
David Dawson and Marcus Kern share lessons learned creating a high-performance mass audience participation system using NoSQL.
-
Master-Builders Have Rich Conceptual Models of Software Design
George Fairbanks stresses the importance of having a good grasp of various conceptual models in order to be a master-builder, translated into development as “learn your software architecture”.
-
Swarm Coding
Phil Hagelberg advises on starting and maintaining user groups doing swarm coding, a form of interactive development in an informal setting.