15 MINUTES RAILS APPLICATION
summary
A simple party-and-invite app gets scaffolded with Rails, OmniAuth Facebook login, migrations and a Heroku deploy but the 15-minute demo actually requires 16 manual actions and ends up taking about 75 minutes to be usable. Scaffolds hide brittle controller logic, tests break on mixed create/find workflows, mail and validation dependencies complicate specs, and legacy apps surface low Code Climate scores (examples down to 1.5). Advice: codify conventions, add presenters/decorators/service objects and teach newcomers to avoid the quick-and-dirty pitfalls. 15-minute scaffold OmniAuth Facebook login Heroku deploy
AI-written summary · about
chapters (13)
- 0:00Introduction to 15-minute Rails app
- 1:41Building the Club Bouncer app
- 2:23Adding authentication with OmniAuth
- 3:53Fixing scaffold and helper issues
- 4:57Inviting users to parties
- 6:26What went wrong in the demo
- 7:30Testing challenges in Rails
- 9:43Legacy Rails problems and code quality
- 12:19Rails for startups and beginners
- 13:43Rails as a foundation for frameworks
- 14:26The Rails community structure
- 15:47Teaching Rails best practices
- 16:40Q&A session
related talks
41mOff the Tracks - Challenging the Rails Mindset
39mExploring Rails anti-patterns
36mBuilding a Rails app live with AI
40mMaking a Rails App with 140 Characters (or less)
08mFrom a spreadsheet to a Rails app in 5 minutes
32mImplementing Rails 3.1...
29mQuick and Dirty Apps with Sinatra, DataMapper, RestClient & Heroku
30mRails Sojourn: One Man's Journey
