Thursday TechTalk – Defects

Defects – When your code doesn’t do what you wanted it to do.

This happens when the developer makes a mistake when creating the code.  (there are many other causes but not the point here)

So, to have developers check the code until there are no defects?  Or to release the code quickly to the testers so they can run it through all the tests and determine if there are defects?

There are other options – more code reviews by senior developers to find the defects, or automated tools that check for common defects.

But the question remains…is releasing code with zero defects the goal?

This will be a good topic for a whiteboard session and a healthy, respectful debate.  Soon.


About workingtechmom

busy, happy, loving life Drop by and leave a message.
This entry was posted in busy mom, corporate jobs, life, tech mom and tagged , . Bookmark the permalink.

2 Responses to Thursday TechTalk – Defects

  1. bulldozer00 says:

    I think zero defects is an unrealistic goal because “absence of evidence” is not the same as “evidence of absence”. It ultimately comes down to economics; sort of like trying to achieve an availability of .99999999999. How much time and money are you willing to invest in attempting to achieve the impossible? Even goals like 1 defect per 1000 lines of code are hard to achieve and, more importantly, measure.

    • All good points. I used to think the economics were in favour of releasing code to testers quickly and letting them find the issues. Now, I’m questioning my own logic.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s