STPCON

"Did you think you were going to be a salesman when you signed up to be a tester?" @mikelyles #STPCon

— Curtis Stuehrenberg (@cowboytesting)2013-10-23 14:23:53

@tvaniotis #STPCon http://t.co/eVvcLQV14p

— JeanAnn Harrison (@JA_Harrison)2013-10-23 14:12:06

Cultural factors trusting env, ability to embrace failures to learn, working directly with dev. @tvaniotis #STPCon

— JeanAnn Harrison (@JA_Harrison)2013-10-23 14:11:10

Structure factors: continuous deployment, incremental rollout, & more @tvaniotis #STPCon

— JeanAnn Harrison (@JA_Harrison)2013-10-23 14:09:46

2/2 when we fail to learn from problems after release (of software) anti-pattern for #testers #STPCon @tvaniotis

— JeanAnn Harrison (@JA_Harrison)2013-10-23 14:07:59

Testers fall into anti patterns: deploy & forget, let ops deal with it, let IT deal w/it, ignoring the value of data, 1/2 @tvaniotis #STPCon

— JeanAnn Harrison (@JA_Harrison)2013-10-23 14:05:54

RT @PerfBytes: @bradjohnsonsv "Continuous Performance: the path towards a performance culture" @soasta #stpcon

— Toby Sinclair (@TobyTheTester)2013-10-23 14:04:03

#TDD tests, do these tests have business value rather than just passing the developed software? @tvaniotis #STPCon

— JeanAnn Harrison (@JA_Harrison)2013-10-23 13:58:46

To reduce the level of risk then reduce the "pace of dev" still risky but dev is more predictable btwn releases. @tvaniotis #STPCon

— JeanAnn Harrison (@JA_Harrison)2013-10-23 13:54:50

What is the role of #testing when release to prod is less than a month?@tvaniotis #STPCon

— JeanAnn Harrison (@JA_Harrison)2013-10-23 13:51:49