What causes bugs.

A coworker sent around this survey today. I thought I'd share my response and also see what the ASP.NET community thought. This is bound to be a hot sports topic so feel free to go nuts. :)

In your opinion, what are the top 10 reasons software bugs occur?

You’ll notice that each one leads to the next one.

10. Poor training. (coding, business analysis, tools, infrastructure etc…)
9. Laziness – the desire to use the easiest to implement solution.
8. Compromises made in req/design to meet delivery schedules.
7. Coding methodology failures such as bad or missing error handling.
6. Vague or incomplete requirements.
5. Misunderstanding of the requirements.
4. Poor design.
3. Misapplication of technology. (Components, products, techniques)
2. Lack of testing.

And the number 1 reason for software bugs is…

1. Change: to requirements, infrastructure, tools etc., because it introduces the likelihood of all of the above to happen.

 

Published Thursday, June 10, 2004 6:41 PM by findleyd

Comments

# Take Outs for 12 June 2004

Saturday, June 12, 2004 6:32 PM by TrackBack
Take Outs for 12 June 2004

# re: What causes bugs.

Friday, July 30, 2004 12:49 AM by Ed
Gödel’s Incompleteness Theorem.

That's the ticket.

Cheers

# re: What causes bugs.

Friday, July 30, 2004 4:25 AM by laurence timms
I would have added

0. Absence of adequate change management.

Face it: change happens. Requirements do evolve. It can't be avoided! Have you ever worked on a project where change did not occur?

# What causes bugs? Change.

Friday, July 30, 2004 5:33 AM by TrackBack
What causes bugs? Change.

# What causes bugs.

Friday, July 30, 2004 11:09 AM by TrackBack
Source: David Findley's Blog I really like these Top 10 reasons software bugs occur! Number 1 is absolutely correct IMHO!

Leave a Comment

(required) 
(required) 
(optional)
(required)