PNSQC

If there is no cost to failure, fail. It's cheaper and faster - Jeffrey Robinson #pnsqc

— umckinney (@umckinney)2012-10-08 13:34:02

#pnsqc. Robinson talk. Low risk, high uncertainty, then experiment with options, feel free to fail, don't form a committee.

— Aashish Vaidya (@aashishvaidya)2012-10-08 13:33:31

Code coverage should be a probe, not a goal. Treat every missed block as "bad", not every covered block as "good" - roseberry #PNSQC

— moss drake (@mxmoss)2012-10-08 13:33:21

Low risk + high uncertainty = fix and accept failure may occur + selected algorithm may be suboptimal - Jeffrey Robinson #pnsqc

— umckinney (@umckinney)2012-10-08 13:32:28

@aJimHolmes heh - I take notes by tweeting! Then go back & read later. #PNSQC

— Pete Walen (@PeteWalen)2012-10-08 13:31:43

updated TESTHEAD: Live From Portland, It's #PNSQC !!! http://t.co/Isi7Gt1P In breakout session, talking about risk vs. uncertainty.

— Michael Larsen (@mkltesthead)2012-10-08 13:31:32

zero Open Source talks at #PNSQC. 8 from Microsoft, 5 from Intel, 4 from McAfee. 2005 PNSQC I presented in a dedicated Open Source track

— Chris McMahon (@chris_mcmahon)2012-10-08 13:31:16

#pnsqc. Jeffery Robinson talk. Low risk, low uncertainty - just do it, don't form a committee.

— Aashish Vaidya (@aashishvaidya)2012-10-08 13:30:32

Low risk + low uncertainty = fix, not analyze - Jeffrey Robinson #pnsqc

— umckinney (@umckinney)2012-10-08 13:30:26

RT @DocOnDev: "Americans write slightly worse than they draw. The difference is we know we can't draw." - @mheusser #pnsqc

— Michael Larsen (@mkltesthead)2012-10-08 13:29:58