Making the implicit explicit
summary
Argues that demos must include salience, prototypicality and mapping rather than isolated code: shows API demos must include authentication, contrasts VMs vs containers to place Kubernetes in context, models useful tooling like oh‑my‑zsh and nvmrc, demonstrates editor/CLI shortcuts (option‑left, Ctrl‑E) and clipboard managers (Copy’n’Paste), and recommends live troubleshooting—show the mistake, show the diagnosis—while avoiding tool‑shaming and unsupported omissions.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:09What do people know
- 2:14Epistemic goals
- 3:27The WHO
- 5:33Learning
- 6:10Salience
- 9:00Mapping
- 10:31The pyramid
- 11:39Epistemic proof
- 12:12Lists
- 12:47Sandwiches
- 13:33Theory vs Practice
- 13:50Practice vs Theory
- 14:48Dapper Dan
- 16:07Teachable moments
- 16:37Teaching skills in context
- 17:00Show keyboard commands
- 18:05Clipboard managers
- 18:31Copy and paste
- 19:15Most people dont know
- 19:33Make people good developers
- 19:50Show how you fix mistakes
- 21:21Tool shaming
- 21:54Demos
- 22:28Conclusion
