~/talk

Essential JavaScript debugging tools for the modern detective

slides:none on file

Demonstrates concrete debugger moves: replace scattershot console.log (the talk cites ~56–67% habitual use) with targeted tools like console.table, styling logs, conditional breakpoints and blackboxing in Chrome DevTools, live expressions, snippets and the local overrides flow to persist quick fixes on production. Shows workspaces and proxying (resource override / Charles) to edit live apps, explains source maps for readable stack traces, and configures VS Code’s debugger for Chrome plus compound launches to step through front end and Node back end together.

AI-written summary · about

  1. 0:00Essential JavaScript debugging tools for the modern detective
  2. 2:10THE PSYCHOLOGY
  3. 2:58reproduce
  4. 5:15elimination
  5. 6:04embrace the bug
  6. 7:18THE CONSOLE
  7. 8:14console.log() with context
  8. 11:26THE DEV TOOLS
  9. 12:24blackboxing
  10. 13:24breakpoints
  11. 14:28logpoints
  12. 14:42snippets
  13. 15:24live expressions
  14. 18:28proxy overrides
  15. 20:38source-map config Development
  16. 21:26source-map deployment
  17. 22:11performance
  18. 23:44accessibility
  19. 25:09dev tools for node
  20. 26:54console.log on the client
  21. 31:56THE CONCLUSIONS
~/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.