Explaining bug writing to management
-
I have been known to write code with bugs in it :-O Does anyone else here do the same? Other programmers understand this: we design, we code, we test, we eliminate bugs etc. the usual stuff. But, how in your experience have you gone about discussing and explaining this process to non-technical senior management? Do they understand that although it may take a day to physically type in some code, it may take a little more time to debug it? I'm interested to hear stories from CP folks, especially positive ones! S [Disclaimer: I have no problems in this respect with my bosses, but inspired by reading Dilbert I wondered about other people's experiences]
-
I have been known to write code with bugs in it :-O Does anyone else here do the same? Other programmers understand this: we design, we code, we test, we eliminate bugs etc. the usual stuff. But, how in your experience have you gone about discussing and explaining this process to non-technical senior management? Do they understand that although it may take a day to physically type in some code, it may take a little more time to debug it? I'm interested to hear stories from CP folks, especially positive ones! S [Disclaimer: I have no problems in this respect with my bosses, but inspired by reading Dilbert I wondered about other people's experiences]
It's all to do with complexity and it has taken two years to get my manager to appreciate this. Of course, now he finallt does the site is closing.... X| Elaine (obfusticating fluffy tigress) The tigress is here :-D
-
I have been known to write code with bugs in it :-O Does anyone else here do the same? Other programmers understand this: we design, we code, we test, we eliminate bugs etc. the usual stuff. But, how in your experience have you gone about discussing and explaining this process to non-technical senior management? Do they understand that although it may take a day to physically type in some code, it may take a little more time to debug it? I'm interested to hear stories from CP folks, especially positive ones! S [Disclaimer: I have no problems in this respect with my bosses, but inspired by reading Dilbert I wondered about other people's experiences]
I have a real problem accepting how some programmers create so many bugs. To be frank it dumbfounds me. Sam Woodward wrote: we design, we code, we test, we eliminate bugs etc. To me this suggests their was something seriously wrong in the design stage. (also where is "we research"). Maybe too many bugs are created because programmers have their heads down typing code, rather than taking a more leisurly thoughtful process, that will achieve superior results. - Managers who don't understand the software development cycle are a pain, and should not be in that position in the first place. Regardz Colin J Davies Attention: Watch this signature for an upcoming announcement that will affect you.
-
I have a real problem accepting how some programmers create so many bugs. To be frank it dumbfounds me. Sam Woodward wrote: we design, we code, we test, we eliminate bugs etc. To me this suggests their was something seriously wrong in the design stage. (also where is "we research"). Maybe too many bugs are created because programmers have their heads down typing code, rather than taking a more leisurly thoughtful process, that will achieve superior results. - Managers who don't understand the software development cycle are a pain, and should not be in that position in the first place. Regardz Colin J Davies Attention: Watch this signature for an upcoming announcement that will affect you.
ColinDavies wrote: To me this suggests their was something seriously wrong in the design stage. Designs are often not bad as in "won't work". They may be lousy from a technical standpoint, but functional. I think the bugs sneak in when humans try to interpret the design and implement it. -- Arigato gozaimashida!
-
I have a real problem accepting how some programmers create so many bugs. To be frank it dumbfounds me. Sam Woodward wrote: we design, we code, we test, we eliminate bugs etc. To me this suggests their was something seriously wrong in the design stage. (also where is "we research"). Maybe too many bugs are created because programmers have their heads down typing code, rather than taking a more leisurly thoughtful process, that will achieve superior results. - Managers who don't understand the software development cycle are a pain, and should not be in that position in the first place. Regardz Colin J Davies Attention: Watch this signature for an upcoming announcement that will affect you.
-
Any, Regardz Colin J Davies Attention: Watch this signature for an upcoming announcement that will affect you.
-
Any, Regardz Colin J Davies Attention: Watch this signature for an upcoming announcement that will affect you.
-
Paul Watson wrote: Isn't that unreasonable? No Paul Watson wrote: Or are you inspiring for excellence? Yes. If I can give an example Paul, I regularlly get 100% marks or A+++ s for my University assignments. However that is what I aim for. If I happen to make a screw up and drop to a A- (heaven forbid), I don't get upset, I analyse why it happened and try to make sure i won't repeat the same mistakes in the future. Developing software products is no different, if you take a solid logical approach your product should be bug free. However we all know this is difficult to achieve, but programmers should still strive for this, and occasionally it might happen. - I think true software development managers should be trying to build working environments that are both highly productive and develop quality products, just as in a manufacturing manager would do. Complaining to programmers about the quantity of bugs produced really shows the incompetence of the manager themself. Regardz Colin J Davies Attention: Watch this signature for an upcoming announcement that will affect you.
-
Paul Watson wrote: Isn't that unreasonable? No Paul Watson wrote: Or are you inspiring for excellence? Yes. If I can give an example Paul, I regularlly get 100% marks or A+++ s for my University assignments. However that is what I aim for. If I happen to make a screw up and drop to a A- (heaven forbid), I don't get upset, I analyse why it happened and try to make sure i won't repeat the same mistakes in the future. Developing software products is no different, if you take a solid logical approach your product should be bug free. However we all know this is difficult to achieve, but programmers should still strive for this, and occasionally it might happen. - I think true software development managers should be trying to build working environments that are both highly productive and develop quality products, just as in a manufacturing manager would do. Complaining to programmers about the quantity of bugs produced really shows the incompetence of the manager themself. Regardz Colin J Davies Attention: Watch this signature for an upcoming announcement that will affect you.
-
Paul Watson wrote: The IT industry is setting unrealistic goals with product cycles and complexity IMO. Hence the bugs. I'll agree with that. Regardz Colin J Davies Attention: Watch this signature for an upcoming announcement that will affect you.