Posts Tagged: testing


29
May 10

Time Bombs

Ran across this quote recently, thought you might enjoy it:

“Don’t call your defects ‘bugs’. Call them ‘time bombs’ instead.”
- Watts S. Humphrey

From Wikipedia: “Watts S. Humphrey (born 1927) is an American software engineer, key thinker in the discipline of software engineering, and is often called the father of software quality.”

He has a recent book out that looks like it could be good, Reflections on Management: How to Manage Your Software Projects, Your Teams, Your Boss, and Yourself.  Has anyone read it?

[via @jurgenappelo]

“Don’t call your defects ‘bugs’. Call them ‘time bombs’ instead.” – Watts S. Humphrey

24
Jan 10

Are you testing or checking?

Vikas Hazrati posts an interesting thought about testing vs. checking at InfoQ:

Checking is something that we do with the motivation of confirming existing beliefs. [...] Testing is something that we do with the motivation of finding new information.”

So when you “test” your software, are you really testing? Or are you just checking?


29
Jun 08

Technical Debt

Johanna Rothman writes about tracking the stuff you can’t fix today, but need to someday:

Technical debt needs to be as visible as everything else. Maybe more so, because the more debt you have, the slower any future development will be.