Why the next big thing sucks
summary
Argues that chasing every new library wastes time and that steady focus plus a clear vision yields lasting success, showing concrete examples: history.js implements the HTML5 history API with fallbacks, docpad is a Node.js CMS that publishes a roadmap and open docs to recruit contributors, and competition from Y Man (Google) does not kill projects if they solve different problems; claims higher rates, community funding, and real deployments as measurable outcomes.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:30Pro the Beginning
- 5:32Detach
- 8:25Solving problems
- 10:50Disruptive technologies
- 13:55Create the disruptive stuff
- 19:15Working full time
- 23:47Mindset of success
- 27:40DocPad
- 32:40Open Source
- 34:07Jack Ill
- 36:40Interview with Benjamin
- 38:31Bens wife
related talks
22mMake Web Not War
43mGood or bad - a key skill for developers
26mStop Solving Problems
21mEmbracing Failure
41mCynicism Doesn’t Build Products
20mFailing Can Be Good! Bringing a Growth Mindset to Every Project
32mMiss the forest for the trees: How frontend developers fail to be engineers
59mDo You Know Da Wae