STARWEST

What was introduced architecturally to deal with this functional or performance problem? This may have a big impact. @grabnerandi #StarWest

— Claire Moss (@aclairefication)2013-10-02 15:10:16

“@alanpage: Awesome crowd at my #starwest keynote. http://t.co/1wMVp2nlZh”

— 행복한앙마™ (@open_comm)2013-10-02 15:09:19

Hanging a test strategy is great, but you can leave the details to be figured out informally by those smart testers you work with. #starwest

— Kwality Rules (@KwalityRules)2013-10-02 15:08:59

@saucelabs having a great time at #starwest

— Freakinlizards (@freakinlizards)2013-10-02 15:07:34

Ohai, #starwest: Want to see a robot play Angry Birds & test your iPhone using #selenium? Stop by after lunch! http://t.co/949nc1lHnY

— Sauce Labs (@saucelabs)2013-10-02 15:07:21

RT @melissatondi: #STARWEST ROI = benefit-cost/cost. Don't confuse benefits with ROI. Brilliant! #dorothygraham

— Tim Western (@Veretax)2013-10-02 15:07:20

Referencing book The Phoenix Project @grabnerandi #StarWest

— Claire Moss (@aclairefication)2013-10-02 15:07:15

RT @aclairefication: Build code that is testable by understanding how hard testing is. @grabnerandi #StarWest

— Tim Western (@Veretax)2013-10-02 15:07:14

#STARWEST ROI = benefit-cost/cost. Don't confuse benefits with ROI. Brilliant! #dorothygraham

— Melissa Tondi (@melissatondi)2013-10-02 15:07:02

Build code that is testable by understanding how hard testing is. @grabnerandi #StarWest

— Claire Moss (@aclairefication)2013-10-02 15:06:53