|
PureBytes Links
Trading Reference Links
|
"That programmer is probably not assigned to the problem in the first
place. He is working on something more important, a new feature.
By the way, that same programmer is adding his own brand new bugs to
the software with every line of code he alters or adds!!"
Programmers always gets assigned bugs in a project. Projects that only
reserve time for new features aren't well designed and probably suffer from
feature creep. Bugs are just as important as new features. All major methods
of development being used today - waterfall, iterative and even extreme
development reserve a significant amount of time to fix bugs. But you're
right that all software ships with bugs -- it's the quantity and quality
that count. Not all software is shipped with easily recreatable GPs and not
all software ships with incorrect output bugs like TS4 did and TS5 does (TS6
too probably). Good shops should strive to fix ALL the bugs though service
pack releases in the fastest time possible. I think iterative development
process develops the most stable software. But it has to be designed right
and it ** has ** allow adequate time for bug fixing. But you have to have
integrety at the top to and a comittment to hiring good people who know how
to build good software.
-----Original Message-----
From: Ernie Bonugli [mailto:ebonugli@xxxxxxxx]
Sent: Monday, December 17, 2001 8:41 AM
To: omega-list@xxxxxxxxxx
Cc: Jim Wixson
Subject: Re[2]: variable declarations within EL?
Hello Jim,
Knowing what we know about managing complex large software development
projects, you learn to accept the bad for the sake of the getting at
the good stuff.
On my last commercial project, we developed and sold thousands of
copies of a program. Throughout my involvement we maintained a constant
large # of Software Trouble Reports. No matter how hard, and late into
the night we worked, we were never able to put a dent on the number of
problems. The program is still a success and is being used to thruout the
states. It is difficult to justify $wise, a staff to just
fix problems. You can justify adding features and in doing so, you
can take care of the bugs. Thereby you get the never ending story.
Programming staffs concentrate on the severe problems, those
abnormally terminate the app, or corrupt the data base. It quickly becomes
apparent that you will never be able to fix those countless little bugs.
Unless the programmer stumbles into the problem, recognizes it a
problem, and is able to replicate it, the problem will not get fixed.
That programmer is probably not assigned to the problem in the first
place. He is working on something more important, a new feature.
By the way, that same programmer is adding his own brand new bugs to
the software with every line of code he alters or adds!!
So with this experience, you learn to accept TS. I kinda like it. I think
it will be difficult to replace it with something that is better and as
as stable. We forget that TS has solved 1,000,000,000s of problems
since it first release.
Best regards,
Ernie mailto:ebonugli@xxxxxxxx
|