Emerge-ncy
summary
Argues that emergence requires built-up tacit knowledge, not chasing tools; recounts a personal diagramming project that cycles through JavaScript → CoffeeScript → ES2015/Babel with package swaps (npm, Bower) and build tools (grunt, gulp, browserify) over three to four months and still remains unfinished, then moves to webpack. Uses the hydraulic moniac accurate to 2% as a model for intuition and shows experiments where patterns form unconsciously, urging make mistakes to gain experience.
AI-written summary · about
chapters (11)
- 0:00Introduction and thanks
- 1:24Emergence in development
- 3:09Industry change challenges
- 6:20Tool overload frustration
- 7:46Fear of the unknown
- 8:49Fear of blank page
- 17:59Tacit knowledge and emergence
- 25:30Expert intuition
- 37:04Building tacit knowledge
- 41:58Conference takeaways
- 45:40Q&A session
related talks
34mTowards a simpler JavaScript ecosystem
49mI'm good at JavaScript, I swear.
11mJavascript Tooling - The Evolution and Future of JS & Front-end Build Tools
38mJavascript Considered...Useful
52mA taste of EcmaScript 6: the language and the tools
53mArchitecting Robust JavaScript Applications
19mStop writing code
43mA moment's reflection