Exploration Through ExampleExample-driven development, Agile testing, context-driven testing, Agile programming, Ruby, and other things of interest to Brian Marick
|
Sat, 27 Mar 2004[Update: added a title for fear the lack of one would break some aggregator somewhere.] Tools do seem to be making a difference here. A good bug database, the optimistic concurancy design pattern used in CVS, even something as amazingly simple as SubEthaEdit. It gives one hope that some what seems so hard may only be a misunderstanding about how to frame up the work. There's technological determinism, vividly displayed in the 90's proclamations that the internet would "route around" all political blockages and empower people all over the world and make participatory democracy inevitable. There's social determinism, the notion that, say, social class drives everything, or that managers need not be expert in the business they manage, or that problems in software projects can be understood with reference only to the people involved: what universal behaviors are they exhibiting? The view I subscribe to is that the world is a big feedback-ey mess. The technological affects the social affects the material affects the conceptual affects the technological... One of the attractive things about the Agile methods is the emphasis they place on the material world. People are not just conceptual entities processing information. They are embodied, living in a physical space that affects what they do and how they think. Hence the emphasis on the tactility of 3x5 cards, on the open workspace, on information radiators. Perhaps the agile methods will not just produce more satisfying software quicker. Perhaps they'll shift us geeks away from a too abstract - a too unidimensional - view of the world. (See also this post from Michael Hamman.) |
|