FredOak3 wrote:
Yea, I just nailed for one today. I wrote this app about a year ago that this group of users pussyfooted on testing for 6 months. We finally went live with it and all of sudden they wanted all these changes.
I've been a software developer for thirty years. I'm afraid this comes with the territory. It used to drive me up the wall years ago too. However, part of the problem is that end users aren't aware of what can be done with software. It isn't until they start using something that they "thought they wanted" that they start discovering all the shortcomings of it - e.g. it works 95% of the time but it can't handle 5% of scenarios. Also end users start thinking... "well this is good, now if it could only do such a thing as well it would be the dogs b*".
Managers are often to blame too - they draw up the specifications for software without often being familiar with the real day to day work done by their subordinates who will use the software - this is a recipe for failure. It is always best if you can cut out the middle-management and talk to the people who actually do the job day to day.
The worse fixes are those that totally undermine the basis of the software and you need to rewrite core modules and virtually end up rewriting the lot. Sometimes this isn't a bad thing though... if you are getting paid for all the changes.
_________________
I've left WP indefinitely.