VelocityConf

RT @wickett: RT @shrikeh: Measure in terms of "time to glass". You have 1000ms to give the users something #velocityconf

— Brian Livingston (@bl1v1ng)2013-11-15 09:20:23

Static code analysis, using tools like brakeman #velocityconf

— James Wickett (@wickett)2013-11-15 09:20:04

We put perf tools in our deploy and build env, but not security tools #velocityconf

— James Wickett (@wickett)2013-11-15 09:19:02

RT @jonathanklein: Slides and links from my #velocityconf talk: http://t.co/MBySJZVXG1

— Miguel. (@miguelcnf)2013-11-15 09:18:57

Note to self : investigate User Timing Marks in WebPageTest #velocityconf

— Perry Dyball (@perrydyball)2013-11-15 09:18:31

RT @Souders: Read @igrigorik's High Performance Browser Networking book online for FREE! http://t.co/A5pCF2LjOd #velocityconf

— Richard Taylor (@moomerman)2013-11-15 09:18:30

Sec Monitoring in prod is low hanging fruit (fail2ban, rkhunter, auditd), More interesting is security in the build pipeline #velocityconf

— Michæl Brunton-Spall (@bruntonspall)2013-11-15 09:18:19

Virus scan your artifacts as you go, ClamAV + Jenkins #velocityconf

— James Wickett (@wickett)2013-11-15 09:17:56

RT @Souders: Read @igrigorik's High Performance Browser Networking book online for FREE! http://t.co/A5pCF2LjOd #velocityconf

— Ido Safruti (@safruti)2013-11-15 09:17:31

RT @addyosmani: Grunt-UnCSS: Remove unused CSS from your project builds https://t.co/yoiIdSgH5Z #velocityconf

— Walmik (@_walmik)2013-11-15 09:15:49