What your QA colleagues are talking about right now (online)
For those of you not on Twitter (yet), there's a constant party happening around the world. It's an intellectual party of testers and you're invited.
Here's some of the chatter (and people) worth following:
Michael Bolton (@michaelbolton): "Two more GREAT reads on topic: /Sciences of the Artificial/ (Simon) and /Mistakes Were Made (But Not By Me)/ (Tavris/Aronson)"
James Bach (@jamesmarcusbach): "I'm doing a talk at the Pacific Northwest Quality Conference called "The Myths of Rigor." To prepare, I'm doing it first in NZ, this week."
Dale Emery (@dhemery): "People don't prefer "confidence without expertise." They prefer confidence, mistakenly thinking that it indicates expertise"
Hillel Glazer (@hi11e1): "Learned an essay I wrote on "agile development as a service" will be in the forthcoming "CMMI for Services" text book. Bio and pic too. #CMMI"
Payson Hall (@paysonhall): "Building Risk Mgt Talk for RiskSIG Conference in Santa Clara 9/24 and 25 based on my article http://www.cutter.com/offers/riskparadox.html"
Steve Smith (@stevenmsmith1): "commented on @drbret's (Bret L. Simmons) post Do Your People Ever Tell You No? http://bit.ly/172IrD. Worth reading."
Jerry Weinberg (@jerryweinberg): "tradeoffs behind implementing standards: The Aremac Project tells what happens when you don't follow standards"
Shrini Kulkarni (@shrinik): "Release readiness criteria - it is like asking when someone is ready for "marriage" - a vague analogy but I think it says it all"
Matt Heusser (@mheusser): "Working on an editorial about impossible questions ("why didn't QA find that bug?") -- wanna review? drop me a note."
Antony Marcano (@antonymarcano): "When I wrote about the telephone game http://is.gd/1PdOu - this is exactly what I meant... http://is.gd/1PdRg"
Ward Cunningham (@wardcuningham): "I love watching Elisabeth Hendrickson explain Exploratory Testing. http://bit.ly/Nev0B"
James Lyndsay (@workroomprds): "Emergent behaviours are frequently more interesting than predefined behaviours."
Adam Goucher (@adamgoucher): "'where i write' (http://bit.ly/73zW3) is a neat idea. 'where i code' or 'where i test' might also be interesting"
Ben Simo (@qualityfrog): "I selected more expensive clothes washer for features I don't use. Now just want fewer features and simpler UI."