100 MVPs
summary
Reports lessons from roughly 100 MVPs built by about 80 students in a 12‑week bootcamp that requires Ruby on Rails, Postgres, user signups and three DB tables. Projects use Google Maps and external APIs, split into three maker types — grand visioners who overreach, tailors who scope precisely, and sculptors who perfect one feature. Students log ~300+ concentrated hours per project; very few continue after class and only one significantly ships and gains users.
AI-written summary · about
chapters (19)
- 0:00100 MVPs journey intro
- 2:32Ideas for MVPs
- 5:02Students' MVP decisions
- 7:11Polished features vs winners
- 8:16Three MVP approaches
- 11:28Technically impressive MVPs
- 13:41Why most MVPs never reach the market
- 14:48Confidence in junior devs
- 16:23Vision versus execution
- 18:09Customer feedback role
- 20:17Passion driving MVPs
- 21:27Bias in idea validation
- 23:02Continuous learning importance
- 24:49Recruiting from bootcamps
- 26:14Vision vs execution in startups
- 28:04Disciplined creativity
- 30:26Demoralization in teams
- 31:36Culture via MVPs
- 33:03Q&A
related talks
17mUsing App Competitions to Promote your API
42mMasterclass: The right path to ML
01h 47mTraining the Trainers
33mRapid prototyping with teenagers
21mHow not to end up your app to a hot mess of spaghetti Carbonara
38mGrow Your Team In 90 Days
40mPanel: Teaching the Next Great Developers
23mWhat I’ve Learned Teaching Postgres to 200+ field engineers at Microsoft