~/talk

Optimise your Web Development Workflow

Talkat ffconf 2016 · 2016-11-10..11-11· [developer-experience, web-performance]
slides:none on file

Live demos show Chrome DevTools actually doing things: native Node.js debugging attached to a running process with breakpoints and live edit, an in-DevTools terminal that runs node, and a filesystem-backed workspaces 2.0 that writes files and triggers build tasks. Performance tools include per-line CPU profiling, FPS and paint profilers, and a new CSS coverage recorder that marks unused rules after arbitrary interactions. Several experimental features work during the talk and most demos succeed.

AI-written summary · about

  1. 0:00Start
  2. 4:24LAYOUT EDITOR
  3. 6:23CUBIC BEZIER EDITOR
  4. 7:21PERFORMANCE
  5. 8:50PAINT PROFILER
  6. 10:40LINE LEVEL PROFILING
  7. 12:24CONSOLE TIMING
  8. 13:04TIMELINE MARKING
  9. 15:11DEVELOPMENT WORKFLOW
  10. 20:01CUSTOMISING
  11. 23:27CONSOLE API
  12. 24:02REQUEST BLOCKING
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 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
?
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.