PNSQC

RT @chris_mcmahon: zero Open Source talks at #PNSQC. 8 from Microsoft, 5 from Intel, 4 from McAfee. 2005 PNSQC I presented in a dedicate ...

— moss drake (@mxmoss)2012-10-08 13:40:30

Robinson talk at #pnsqc. When in high uncertainty, high risk situation, then is right case for analysis.

— Aashish Vaidya (@aashishvaidya)2012-10-08 13:40:28

RT @umckinney: We tend to be overly risk averse and conflate risk with uncertainty - Jeffrey Robinson #pnsqc

— Michael (Doc) Norton (@DocOnDev)2012-10-08 13:39:41

We tend to be overly risk averse and conflate risk with uncertainty - Jeffrey Robinson #pnsqc

— umckinney (@umckinney)2012-10-08 13:39:17

Functional testing and automated code coverage are separate. Can have overlap, but different goals. (My takeaway) #pnsqc

— Jason (@mynwexperience)2012-10-08 13:38:03

@aJimHolmes I thought I saw you in the background ... #PNSQC

— mheusser (@mheusser)2012-10-08 13:37:47

#pnsqc. Robinson talk. When risk is hi, uncertainty is low. Make a quant judgment, pick one option out of many. New > old junk.

— Aashish Vaidya (@aashishvaidya)2012-10-08 13:37:42

High risk + high uncertainty = analyze it. - Jeffrey Robinson #pnsqc #thereisapatternhere

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

I end up selling a copy of @ithoughtsapp at just about every conference I attend, and #pnsqc is no exception. Should I ask for a commission?

— Ian Dees (@undees)2012-10-08 13:37:04

High risk + low uncertainty = pick an option + accept possibility of suboptimal selection - Jeffrey Robinson #pnsqc

— umckinney (@umckinney)2012-10-08 13:35:12