Please reconsider your evaluation of your product as a 'robust' application. No finished product should create it's own registry errors. Especially ones that that will crash the app when you populate a list box. It's pretty sad and it makes me wonder what idiot project manager or QA department let it slide. When I call and it is common enough a problem that you have me blow out the registry and then call it fixed that's a really bad sign: it should be fixed by the next release/patch. I mean really. Also there is functionality that will follow logically (from a users point of view) simply from the options/functionality you include. For example if you give the option to create billing address for a contact and I have to call your support line to find out the extra work I have to do to actually get the billing address included on bills that's not OK. If your out of the box application includes these flags why doesn't it use them or if it needs to be configured to use them, shouldn't that information be simple to find?
Now that any software developers are all foaming at the mouth let me say this: I do understand the development process, I do know that PMs, clients and presidents of companies and other people in positions of power will push things through unfinished/incomplete/broken, I have had it happen to me too. But I really hope you are fighting them tooth and nail to be able to deliver complete applications that have been as thoroughly tested as possible. </rant>
Now that any software developers are all foaming at the mouth let me say this: I do understand the development process, I do know that PMs, clients and presidents of companies and other people in positions of power will push things through unfinished/incomplete/broken, I have had it happen to me too. But I really hope you are fighting them tooth and nail to be able to deliver complete applications that have been as thoroughly tested as possible. </rant>
ummm.....
Date: 28 Jul 2004 17:44 (UTC)Re: ummm.....
Date: 28 Jul 2004 18:12 (UTC)