PDA

View Full Version : Professional programming = bug-fixing?



Carlos
12-07-2001, 04:43 AM
Professional programming is not always that creative work I imagined ...
What's your opinion?

Yoshi
12-07-2001, 01:04 PM
Good programming and testing means good programmers. Bugs usually occured in new-comers.
-----------------------------------------------
Engineer223

Shade
12-07-2001, 02:24 PM
do you really think so?

i haven't discoverd yet a good, complex bugfree program -> the complexer a program is the more bugs are in it

gamegod3001
12-07-2001, 03:24 PM
Date: 10/7/2001
To: Cprogramming.com members/mods/amin/guest
From: Gamegod3001
re: Professional programming = bug-fixing?

>Good programming and testing means good programmers. Bugs usually occured in new-comers. <

>i haven't discoverd yet a good, complex bugfree program -> the complexer a program is the more bugs are in it<

Your both right, a new comer has would have the tendency to have more bugs in there program, and complex programs by there very nature have more bugs.

Unregistered
12-07-2001, 04:12 PM
A lot of industry documentation says that 80% of a developer's time is spent bug-hunting and fixing, and only 20% on other ventures (i.e., new development). So to say that professional programming = bug fixing is actually fairly accurate.

I'd be inclined to wonder though, how much of the bug-fixing is a result of errors being introduced out of carelessness and how much out of functionality/compatability issues. I.e., how many bugs can be prevented on the front end via "good coding practices" (coding standards, white box testing, etc.), and how many can only be found via functionality and system-level testing.

I would think, especially if programming was my professional "day job" that I would want to create as error-free code as possible so that I could spend the better part of my day on new endeavours. Realizing this, however, there's still a big industry backlash against developers performing "testing" functions. It seems like a cycle:
-- developers developer because that's what they like to do
-- developers don't test because that's not what they like to do
-- testers test because ... they're testers
-- testers find errors that developers could have found if they had tested, document these errors, then pass them back to developers
-- developers now have to address documented errors, this time with the attached paperwork, and then re-submit the code to testers
-- rinse and repeat ;)

Almost makes ya wonder which came first -- the chicken or the egg.

gnu-ehacks
12-07-2001, 08:04 PM
>>Bugs usually occured in new-comers.

Uh...That's not entirely true. Bugs can pop up anywhere. Big things like Linux even have bugs. It's all part of programming, although I agree that good coding and testing results in a good program. (mostly)

Yoshi
12-07-2001, 08:06 PM
You are correct. Bugs are nearly impossible to eliminate.
-------------------------
Engineer223

lightatdawn
12-07-2001, 08:49 PM
"My program doesnt have bugs; It just develops random features."


A few technical terms one might find useful:

Keyboard - The standard way to generate computer errors.

Mouse - An advanced input device to make computer errors easier to generate.

Disk Crash - A typical computer response to any critical deadline.

System Update - A quick method of trashing ALL of your software.

Stack - A memory space used to entertain the programmers and management by overflowing or being subjected to mismatched PUSH/POPs.

Bug - An aspect of a computer program which exists because the PROGRAMMER was thinking about Jumbo Jacks or stock options when s/he wrote the program.

Fortunately, the second-to-last bug has just been fixed.

Aran
12-07-2001, 08:57 PM
the scary thing is.. that's completely true.