On Tuesday 03 July 2007 12:12, Matthew Jarvis wrote: <snip> > > Recently I was told by a programmer I deeply respect that my application > > can't work because I haven't defined what I want it to do. Of course, > > this is true, I've discussed what I want, but not *defined* it.
Hi Matthew! > When I do consulting projects I always start off with a yellow pad and <snip> > "I want to help my fellow professionals assist in the treatment of > patients by collecting information suitable to tracking their treatments > and response to such treatments. We will then use this information for > future research and treatment options." That's good. > On the other hand, what your programmer person might have meant (and > pardon me for being blunt) is a polite way of saying that what you have > written for an app is a total mess lacking any sort of logical flow or > consistency. It may do a lot of 'stuff', but it doesn't meld all of that > into anything cohesive. Trying to be as critical and unattached as you > can - would *you* want to use your program? Actually, I had a huge collection of VFP screens and tables set up that didn't do *anything*. Looked nice, though. Stephen hit it in his post. The rest is just details and eye candy. Of course, there has to be some kind of a "win" for the user or he/she won't use the app and thus provide data. -- Regards, Pete http://www.pete-theisen.com/ _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
