(no subject)
Jan. 15th, 2002 09:35 amNo coder is interested in the results of testing.
If a bug is a "real" bug, the coder will have found it himself, and already fixed it. Bugs found by testers are by their very nature trivial. "No one will see that," says the coder. "Or if they do, they won't care."
Coders find the fixing of bugs to be demeaning. How much better to write new features into the code, features that may cause more purchases when they are advertised. No coder wants to spend his time attempting to decipher code written weeks or months ago, simply to fix trivial bugs.
One imagines it would be the job of management to ensure that bugs become fixed. This becomes unlikely when management is also a coder.
At this time I have over fifty bugs listed in the bug-tracking database. Some of these bugs date from August; at least one is from June. Perhaps one-third are truly "trivial", things that in fact no one would ever do. Few of my reported bugs are from later than early November, becase at that point I essentially gave up on using the bug-tracking database. What's the point of bothering to enter a bug if it will languish, not only unfixed but un-looked-at?
I would seek employment at another company, but I suspect that the process at any small software company would be more or less the same, and I have serious doubts about my ability to get a job at a larger company without a degree. So I plod on.
No coder is interested in the results of testing.
If a bug is a "real" bug, the coder will have found it himself, and already fixed it. Bugs found by testers are by their very nature trivial. "No one will see that," says the coder. "Or if they do, they won't care."
Coders find the fixing of bugs to be demeaning. How much better to write new features into the code, features that may cause more purchases when they are advertised. No coder wants to spend his time attempting to decipher code written weeks or months ago, simply to fix trivial bugs.
One imagines it would be the job of management to ensure that bugs become fixed. This becomes unlikely when management is also a coder.
At this time I have over fifty bugs listed in the bug-tracking database. Some of these bugs date from August; at least one is from June. Perhaps one-third are truly "trivial", things that in fact no one would ever do. Few of my reported bugs are from later than early November, becase at that point I essentially gave up on using the bug-tracking database. What's the point of bothering to enter a bug if it will languish, not only unfixed but un-looked-at?
I would seek employment at another company, but I suspect that the process at any small software company would be more or less the same, and I have serious doubts about my ability to get a job at a larger company without a degree. So I plod on.
No coder is interested in the results of testing.