What does a mature agile team think of a product (System) defect?

Why not look at the product (System) defect optimistically?

by algorithm , computers can now compose music . , Human Face recognition , Doctor , predict a person's decision on an issue ... and so on.

so Span style= "Color:black" > It is impossible to develop software
negative

because , to be able to have a software , ability to identify all defects in the product (System) , then we must have a " defect-Free software " .
of course , It's never going to happen.

so , defects can never be found out , defects can never be avoided. So how do we look at defects ?

"Any defect in the product (System) is trying to tell us something ".

some of the flaws are telling us , the demands of the user are too unreliable. Some defects are telling us that the software architecture of the product (System) is old. Some of the flaws are telling us that when we write the code , We may still be in a state of sleep ... and so on.

so Span style= "Color:black" > a truly mature Agile team Will think of defects as a good and better " opportunity "

only a truly mature agile team , to Mature , optimistic about " face " defects , " processing " defects , " put down " defects.

What does a mature agile team think of a product (System) defect?