>>Remember guys, Goal #1: Make sure the customers
>>knows what they want. How many times have you
>>heard the specs & shook your head in
>>disbelief!?!?! I find all too often they only
>>think they know what they want.
>
>100 %!
>
>>If you can
>>convince them they have bad gaps then you are on
>>the road to getting reusibility of your objects.
>>
>
>My point is that as VFP programmers, we only come
>in where problems are in nature not prone for
>reusability. Hence the low reusability rate
>Lucien is talking about, and hence the low
>priority in terms of resources that reusability
>should represent for us.

Marc.

I agree 100%. If the customer was in the 'mid stream' as far as what they wanted we could reuse our code. The problem, and it makes complete sense, is that the reason why they want a program written is because they cannot find it anywhere else -- hence a one of a kind (or non-reuseable code) program.

Think about it, if the customer wanted canned code they could buy it off the shelf for (useually) much less then it would cost to have it written specifically for them.

Tom