~/talk

JavaScript’s “+” Operator and Decision Fatigue

Talkat JS Kongress 2017 · on Monday, 2017-11-13· [javascript, developer-experience]
slides:none on file

Claim: the JavaScript + operator produces unintuitive results because ECMAScript runs a long coercion procedure so 2 + "2" => "22" and Infinity + -Infinity => NaN via ToPrimitive/ToNumber rules; about ten to twenty internal steps determine behavior. Performance and reasoning tradeoffs are handled by v8's turbofan JIT, which inlines hot paths. Cognitive parallel: ego‑depletion experiments (cookie vs radish) and a judicial study (parole rates fall from ~65% to 0 before breaks) justify tactics: do hardest work first, schedule commitments, simplify decisions.

AI-written summary · about

  1. 0:00Plus operator introduction
  2. 1:43How plus operator works
  3. 3:10Plus operator examples
  4. 5:24Plus operator edge cases
  5. 7:25Why improvements matter
  6. 8:49V8 TurboFan speed
  7. 10:36Decision fatigue basics
  8. 12:25Willpower depletion study
  9. 14:34Decision fatigue in professional settings
  10. 15:40Judges' parole decisions
  11. 16:44Preventing decision fatigue
  12. 18:32Done > perfect
  13. 19:35Community progress
~/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.