![]() |
|
#10
|
|||
|
Having been a SW engineer for over 30 years, I can tell you there are two major syndromes when it comes to a new release:
1) Releasing too early, rationalizing major bug into minor problems. Crossing our fingers and hoping that the users don't find that use case you know about (they always find it in 5 minutes while it took your testers and dev team 4 months to run into it). The need for revenue outweighs the anger of the end users. 2) Waiting for perfection. Each bug that has a workaround is rated as a major issue. Aesthetic issues are sweated over because the developer has been staring at the same glitch for weeks but in reality users will never see it because it's usually on screen for 5 seconds. The desire to please everyone outweighs everything else. Both are bad. Problem number 1 results in angry users and a bad reputation. But it can be overcome if patches are forthcoming and actually solve problems. Devs are usually motivated to solve the problems once the pressure of release is behind them. Problem number 2 results in demoralized developers who, faced with the impossible task of creating perfection, simply walk away to find a new project. People need goals that are attainable, even if they at first seem impossible. And they need the rewards of their efforts. People actually using their software is that reward. | ||
|
|
|||
|
|