The myth of the “Real JavaScript Developer”
summary
Argues that the “real JavaScript developer” myth is false and gives concrete alternatives: pick tools that solve a problem not trends (example timeline: Grunt→Gulp→Webpack race starting 2012), stop memorizing trivia — many devs still look up splice vs slice daily — and use documentation, peers and targeted searches. Emphasizes iterative work, debugging skills, showing work early (PRs), linters for style, and limits to overtime (productivity falls after sustained 60h weeks). Shows hobby-code wins like JS on a knitting machine and 8‑bit art.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:50I NEED TO KNOW EVERYTHING
- 3:12You still use gulp? You should be using webpack!
- 4:29USE NEW AND SHINY WHEN IT SOLVES A PROBLEM
- 4:57I NEED TO KNOW MEMORIZE EVERYTHING
- 6:15THIS IS NOT A TEST
- 7:08REAL DEVELOPERS USE RESOURCES WISELY
- 8:09YOUR PEERS ARE A RESOURCE
- 8:40My biggest professional development was getting comfortable admitting what I don't know.
- 10:48REAL DEVELOPERS ACCEPT THE UNKNOWN
- 12:07SOFTWARE IS SOFT
- 13:42KNOW HOW TO DEBUG
- 17:48I HAVE TO CODE ALL DAY EVERYDAY
- 20:04DEVELOPERS CAN BE CARPENTERS
- 21:00DEVELOPERS CAN BE PARENTS
- 22:54Constraints are often advantages in disguise. Forget about venture capital, long release cycles, and quick hires. Instead, work with what you have.
- 23:53REAL DEVELOPERS THINK OUTSIDE THE BROWSER
- 26:12REAL DEVELOPERS RESOURCEFUL ACCEPTING CREATIVE
- 26:40BUST THE MYTH. RESHAPE THE NARRATIVE.
related talks
49mI'm good at JavaScript, I swear.
47mThe Politics of JavaScript
35mJavaScript: Enter The Dragon
31mThe Effective Developer - Work Smarter, Not Harder
41mJavaScript, Day 4001
50mThe Effective Developer - Work Smarter, Not Harder
53mIs JavaScript Making Us Better Professionals?
33mFive ways to be a happier JavaScript developer