Successful Speedy MVP Website Development
summary
Claim states a workflow that wins hackathons by narrowing scope, practicing the pitch, and automating deploys. Uses Ruby on Rails, continuous deployment and a one‑feature focus to finish a demoable MVP in seven hours. Describes building paperclip data i/o as a single useful feature that ships and later becomes mainstream, schedules time for rehearsal and testing, and reserves a final third of the slot for polish so the demo actually works.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:12Speedy MVP development
- 1:56speaking to "Rails"
- 3:18How to win a hackathon?
- 3:32PPT for the win
- 5:23How did we win in 2012?
- 9:421 major features
- 10:57ground works
- 11:51build major features
- 12:48build minor features
- 13:39finalize product
- 14:13with perfect pitch deck / demo with meaningful product no bugs, no crash 100% production ready
- 16:49Differences
- 21:49Definition of "Success" Base on those definitions to prioritize the User Story
related talks
40mOptimize for developer speed
23mDeveloping multiple personalities to bootstrap your first product
39mHackathons on Rails
18mReact-ing to Rails: Why Ruby on Rails is the best Stop for Web Developer
41mRiding the Latest Rails for Charity
14mWhat About Ruby On Rails? ... From A PHP Guy
37mReal Developers Ship (a.k.a Tenets for Software Delivery)
30mKeith and Mario's Guide to Continuous Deployment with Rails