yak
[Top] [All Lists]

[yak@collab] Re: Philosophy and System design WAS: Re: [yak@collab]Re: A

To: yak@xxxxxxxxxxxxxxxxxxx
From: Jack Park <jackpark@xxxxxxxxxxxxxx>
Date: Thu, 26 Feb 2004 16:53:44 -0800
Message-id: <403E9518.90406@thinkalong.com>
John Sechrest wrote:    (01)

>Jack Park <jackpark@thinkalong.com> writes:
>
> % But, there is the mantra of XP, which is, among other things, release 
> % early, release often. The nature of that is to get trial balloons out to 
> % the users, with explicit understanding that they are, actually, 
> % participating in the development process by telling you how the product 
> % relates to their goals. Iterate, release often, etc.
>
> % Maybe there's no real metric that says when to abandon a prior mental 
> % machinations, but, in many smallish project cases, hacking design 
> % documents absent any prototyping of major ideas, is probably just as 
> % risky as just hacking prototypes absent design documents.  Go figure...
> % Jack
>
>
>So , did I hear you say:
>
>Define ReleaseEarlyReleaseOften
>
>An ExtremePrograming metric that suggests that you send out
>releases Early and often to get trail balloons out to the users,
>with the explicit understanding that the users are actually
>part of the development process. The Users participate in this
>process by telling you how well the product meets their goals.
>This gives you EarlyFeedbackThruRapidIteration
>
>  
>
Yes. I believe I said something like that. I'd like to parrot Erics 
comments which follow your question and preceed this reply. This all has 
to be done in a trusted way such that you don't lose your clients. Eric 
mentions care for their data. Agreed. Murray talks about the nature of 
clients and their needs. Agreed, and the followups to that which state 
that the program really calls for something like trusted clients, those 
who know what they are getting in to. It wouldn't, as Murray says, do 
for him to toss a buggy Ceryle at, say, an Asimov or Stephen King, but 
tossing it at me and a few others provides the kinds of early feedback 
he has needed to coax things to run better, perhaps earlier than he 
could have by himself. Plus which, he gets a kind of asynchronous 
"paired" programming by bouncing his ideas off people who are in the loop.     (02)

All in all, that yak tribe could morph into a largish group of "paired" 
programmers if we all started posting our projects in places where we 
could trade hacks, ideas, code, testing time, and the warm fuzzies that 
come from watching someone benefit from an occasionally correct comment 
or input.    (03)

Speaking of which, I'm most anxious to see Compendium source code in the 
wild ;-)    (04)

Jack    (05)


-- 
This message is archived at:    (06)

http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=403E9518.90406@thinkalong.com    (07)
<Prev in Thread] Current Thread [Next in Thread>