259
edits
Webdev:Velocity 2009 Notes: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
**Averages don't mean anything, get the median and percentiles. | **Averages don't mean anything, get the median and percentiles. | ||
*Overall | * Optimization (js) | ||
** Running code is slower than not doing anything | |||
** be aware of lookup chains, use locals | |||
** beware of live collections | |||
** avoid the reflow | |||
** writing javascript like it's C makes it faster | |||
* Facebook | |||
** "Test with real users, don't test in the dark." -- WTF (talking about unit testing, not scaling) | |||
* Flickr | |||
** http://www.kitchensoap.com/2009/06/23/slides-for-velocity-talk-2009/ | |||
** automated infrastructure | |||
** shared version control between webdev and IT | |||
** one-step build *and* deploy | |||
** continuous integration server (Hudson) | |||
** dark launches | |||
** ganglia monitoring | |||
*** New code (dev) | |||
**** what metrics will changes, and how! | |||
**** what are the risks, signs something is going wrong | |||
*** Ops | |||
**** be transparent, give devs access to systems | |||
*Overall | |||
** Graphs or it didn't happen | |||
**Measure everything you can | **Measure everything you can | ||
**IT & Webdev/engineering should overlap and have same goals | **IT & Webdev/engineering should overlap and have same goals | ||