~/talk

Building Resilient User Experiences

Talkat Velocity US 2012 · 2012-06-25..06-27· [frontend-architecture, web-performance]
links:none on file
slides:none on file

Large-scale pages separate critical from ancillary services: a failed view counter should not throw a stack trace and block checkout, so code catches errors and renders the rest of the product page while hiding missing widgets with black-box graceful degradation. Practical patterns include moving non-critical pieces into non-blocking AJAX, timing out ads at 400ms and using exponential backoff, plus an error-beacon on templates to graph failed page views in real time.

AI-written summary · about

  1. 0:00Introduction to resilience
  2. 0:31The offline analogy
  3. 1:28Handling online failures
  4. 2:57Critical path vs ancillary
  5. 3:54Graceful degradation
  6. 5:13Etsy's resilience strategies
  7. 7:02UI level resilience
  8. 8:26User messaging strategies
  9. 9:03Cross-functional planning
  10. 10:58Conclusion
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.