velocityconf

RT @pingdom: The ultimate performance tip: Keep it simple and only load what you need. By @bryanmcquade (Google) #VelocityConf

— Jonathan Klein (@jonathanklein)2012-06-25 13:17:58

Alright, on my way to #jfk to #sfo to #velocityconf. It's a #hashtagavaganza!

— Jan Schaumann (@jschauma)2012-06-25 13:17:37

RT @mrembetsy: RT @tlossen: "minimal viable infrastructure: github, rsync, ec2, s3cmd, pingdom" -- paul hammond @ph #velocityconf

— James Wickett (@wickett)2012-06-25 13:17:30

I'm seeing Understanding and Optimizing Web Performance Metrics at Velocity. http://t.co/0LuKVn0R. #velocityconf

— Alfie (@bitsysays)2012-06-25 13:16:54

the real issues we end up experiencing are because we hadn't thought to measure them #velocityconf -@ph

— James Wickett (@wickett)2012-06-25 13:16:54

RT @pingdom: The ultimate performance tip: Keep it simple and only load what you need. By @bryanmcquade (Google) #VelocityConf

— Dits kenny (@kenny_dee)2012-06-25 13:16:40

Best disaster contingency plan: be able to change your infrastructure fast. Optimize for this while there's time. #velocityconf @ph

— Ingmar Krusch (@IngmarKrusch)2012-06-25 13:16:32

RT @tlossen: "minimal viable infrastructure: github, rsync, ec2, s3cmd, pingdom" -- paul hammond @ph #velocityconf

— Jonathan Klein (@jonathanklein)2012-06-25 13:16:15

In first presso by @bryanmcquade Now I'm itching to performance tune using the Critical Path Explorer #velocityconf

— David Lutz (@dlutzy)2012-06-25 13:15:30

RT @tlossen: "minimal viable infrastructure: github, rsync, ec2, s3cmd, pingdom" -- paul hammond @ph #velocityconf

— Michael Rembetsy (@mrembetsy)2012-06-25 13:15:22