there's an old joke: policeman comes across a drunk crawling around under a streetlamp, asks him what's up. drunk says he lost his car keys. so the cop helps him look for a while . . .
. . . but no luck, so the cop asks him, "where's your car, sir?" and the guy points off in the dark. cop says, well, why are we looking over here, when your car is over there?
drunk says, "well, because the light's better here."
drunk says, "well, because the light's better here."
there are folks who would have you believe that the software development movement we're a part of is about what i call broadly "method": structure, process, technique, rules, definitions, steps, algorithms.
i don't believe that, myself. that's why i go on all the time about acculturation, about "the whole geek", about the triple-base of made+making+maker, and so on.
the light *is* better there, under "method". i don't think that's the most likely place we to find the agile car keys, though, so that's not where i'm looking.
i'm off in the dim recesses of community.
i'm off in the dim recesses of community.
i am a geek's geek: i *adore* technique. i find great beauty in structure. i long for algorithm and rules and process.
but all the great moments of my career in agility have come from community, and that's where i am looking for more of them.
but all the great moments of my career in agility have come from community, and that's where i am looking for more of them.
