The problem with solution-description
-
Sometimes bugs come up that are hard to reproduce and even harder to find what caused them. When you actually do find the reason most of the time fixing it is quite easy. The problem is that when I have to relay the cause and solution of such bugs to superiors it all seems so obvious. Somehow seeing 2 to 3 full workingdays spend on a single bug summarized in a small single paragraph is so ... a fitting word doesn't come to mind... sad I guess could describe it. It just doesn't represent the brain-work needed to actually locate the bug. The countless possibilities explored by the mind even during breaks, driving home, quiet moments at home. All that is just disregarded in that paragraph. I have written applications which needed only 5% of the brain-power needed to fix some of those elusive bugs, but those apps were received with awe and shoulder pats. Ah well, comes with the territory I guess . Just wanted to get this of my chest. Regards, Davy
-
Sometimes bugs come up that are hard to reproduce and even harder to find what caused them. When you actually do find the reason most of the time fixing it is quite easy. The problem is that when I have to relay the cause and solution of such bugs to superiors it all seems so obvious. Somehow seeing 2 to 3 full workingdays spend on a single bug summarized in a small single paragraph is so ... a fitting word doesn't come to mind... sad I guess could describe it. It just doesn't represent the brain-work needed to actually locate the bug. The countless possibilities explored by the mind even during breaks, driving home, quiet moments at home. All that is just disregarded in that paragraph. I have written applications which needed only 5% of the brain-power needed to fix some of those elusive bugs, but those apps were received with awe and shoulder pats. Ah well, comes with the territory I guess . Just wanted to get this of my chest. Regards, Davy
A decent project manager (who has programming experience himself) will recognise the difficultly of debugging.
Simon
-
Sometimes bugs come up that are hard to reproduce and even harder to find what caused them. When you actually do find the reason most of the time fixing it is quite easy. The problem is that when I have to relay the cause and solution of such bugs to superiors it all seems so obvious. Somehow seeing 2 to 3 full workingdays spend on a single bug summarized in a small single paragraph is so ... a fitting word doesn't come to mind... sad I guess could describe it. It just doesn't represent the brain-work needed to actually locate the bug. The countless possibilities explored by the mind even during breaks, driving home, quiet moments at home. All that is just disregarded in that paragraph. I have written applications which needed only 5% of the brain-power needed to fix some of those elusive bugs, but those apps were received with awe and shoulder pats. Ah well, comes with the territory I guess . Just wanted to get this of my chest. Regards, Davy
I've got the opposite problem right now. Perfect description and easy to reproduce. - 'Click the button and application does a crash and burn' I'm now into week two of finding the mfw object handle that's being mislaid, sticking it down with the code equivilent of gaffa tape and stopping the runtime error. Joy! :doh:
Panic, Chaos, Destruction. My work here is done.
-
I've got the opposite problem right now. Perfect description and easy to reproduce. - 'Click the button and application does a crash and burn' I'm now into week two of finding the mfw object handle that's being mislaid, sticking it down with the code equivilent of gaffa tape and stopping the runtime error. Joy! :doh:
Panic, Chaos, Destruction. My work here is done.
On Error Resume Next Gets round most things :)
I still remember having to write your own code in FORTRAN rather than be a cut and paste merchant being pampered by colour coded Intellisense - ahh proper programming - those were the days :)
-
On Error Resume Next Gets round most things :)
I still remember having to write your own code in FORTRAN rather than be a cut and paste merchant being pampered by colour coded Intellisense - ahh proper programming - those were the days :)
Baconbutty wrote:
On Error Resume Next
Oneth, if I used o-e-r-n I'd be shot at dawn and my corpse would thrown to the four winds. Twoth, it's in TCL and it's caused by holding a memory reference that's gone awol. When I check that the memory is still valid it goes bang. I have actually half fixed it, finally, this morning. The only problem is now I get an obnoxious, though no-fatal, error when there is no-reference in the first place. You can't win them all. In fact just scraping together a few draws is difficult. :-D
Panic, Chaos, Destruction. My work here is done.