|SUMit Roster Software > Nut's Weekly > April 2000 > Disprovement||Nederlands · Search...|
|Easter Monday, 24 April 2000||February 2000 March 2000 Rust Broken E-Shop May 2000 June 2000|
Last week I started a project at a new customer
I was just happily designing a form when I got an unpleasant surprise.
These gimmicks don't help me, the slow me down. A save button must save, nothing else. Working efficiently is mainly a matter of no distractions, maintain flow (www.asktog.com/...023MaxHumanPerf.html).
Yes, I know that each software release should have added value. But that should not lead to creeping featurism (info.astrian.net/jargon...creeping_featurism). Changes are fine, but they must be improvements.
In addition, the bugs in the old release are well known. As a user I know where they are. By experience I've developed ways to avoid them. Those bugs will probably be solved in the new release, but well, I wasn't not really waiting for those fixes any more. What I will see are yet unknown bugs. What a disaster.
So, my conclusion is: Stop shipping new software releases. My dear ladies and gentlemen software developers: Declare a product to be finished. No more new features, and just ignore the old bugs.
· May 2000
Home · Search...