Everyone who writes safety critical software should read this

[Walter Bright]

On 11/1/2013 6:52 AM, Wyatt wrote:
> "We could, for instance, begin with cleaning up our language by no longer
> calling a bug a bug but by calling it an error. It is much more honest because
> it squarely puts the blame where it belongs, viz. with the programmer who made
> the error.

Although it is tempting to do so, creating a culture of "blame the programmer" 
for the mistakes he's made also creates a culture of denial of problems.

If you want to create quality of software, a far better culture is one that 
recognizes that people are imperfect, and looks for collaborative ways to 
engineer the possibility of errors out of the system. That doesn't work if 
you're trying to pin the blame on somebody.