Kent Beck makes a post on Accountability in practice, in which he points to the Open Quality Dashboard: "I particularly like contrasting the graphs at the bottom of the Analysis tab between projects. I hope other software vendors will publish their quality data." (See also: Slashdot discussion)

Michael Hunter was a codeslinger, but learned that Slow And Steady Wins The Race: "Exploratory testing is a great way to get a handle on an area, and it can be a very effective technique on its own. However, if you treat it as advance scouting and take some time to use your findings to draw up an actual test plan, you can take your testing to the next level."

Phillip J. Eby discovers DocTest and is graced by a revelation: Stream-of-Consciousness Testing. "Ordinarily, I hesitate over every new test, trying to figure out how to translate from the result I want, to a test expressed in unittest-ese. With doctest, however, the testing just 'disappeared' from perception. It was like I was just writing down my thoughts while playing with the interactive interpreter, only it was even better than that, because the interpreter and my notes were a single, continuous stream, and my work was saved in a file where I could edit and re-run it at will." (See also Grig Georghiu's articles Python unit testing part 2: the doctest module and Agile Documentation with doctest and epydoc)