How to be better
summary
Claims that mark progress: write unit tests until they get easier, know the six falsy values, and memorize 21 native array methods (seven mutators, seven accessors, seven iterators). Use JS Lint but only disable rules you can convincingly argue with, treat CoffeeScript as a performance reward not a shortcut, avoid using objects as mutable data dumps and keep object shapes consistent for GC speed, and insist on blocks of free time (ten days or research weeks) to do focused work.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:00How to be better
- 1:20What is getting better
- 2:00When did javascript get hard
- 2:44The World Wide Web
- 5:42Missing a slide
- 6:32The first step
- 7:19The three strands
- 10:05Find something else to do
- 11:28Mastery
- 13:39WTFs
- 16:58Strings
- 17:34Frameworks
- 19:22Use them
- 21:07Quotes
related talks
10mExplains 5 Steps to Get Better at Coding
50mThe Effective Developer - Work Smarter, Not Harder
17mGood to Great
40mThe Best Programmer I Know
23mJavaScript Masterclass
01h 00mBuilding better developers
26mNobody Will Train You But You
26mEvidence Over Advice: Learning Programming Faster Using the Scientific Method