> Yes. For one thing, they're paying the bills. In which case, a successful strategy I sometimes use is to make what they want really expensive, especially if I don't really want to do it :-)
> For another, it may be us who are ignorant and not them. Yes, but you should know if you're ignorant, shouldn't you? :-) In those cases it is necessary to understand enough of their problem domain to provide an adequate solution. This is just basic requirements gathering/elicitation. > No, you never "need" to educate anyone. Sure you do, lots of times. How you go about it is important, of course. > There are some customers who aren't > interested in your reeducation attempts. Agreed! :-) > I do maintain that the customer is always right. However, sometimes it's > indeed possible to "educate" them to make them change their minds about > what's right. Well, I think we're saying the same thing in a different way. (And I'm not talking about trivial things like how they want the UI to be all pink and lilac, BTW <vbg> Sadly, I'm thinking of an actual project) > And sometimes they're too damn stupid for me to allow them to > continue to be my customers. :) :-) Cheers, Jim Cooper ____________________________________________ Jim Cooper [EMAIL PROTECTED] Tabdee Ltd http://www.tabdee.ltd.uk TurboSync - Connecting Delphi with your Palm ____________________________________________ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
