• show you some live coding
• give a talk about “why choose rails”
• before today
• today and tomorrow
web development now
• open-source technologies and tools
• server-side frameworks
• shorter development cycles
with Rails you focus on
• creating functionality, not creating code
• Rails is opinionated
• “If you try to design for the 20 percent of your
target audience who are power users, your design
may be not usable by the other 80 percent of
• if one feature satisfy 20% of your customers - it’s
not worth implementing
• convention over conﬁgurations
• Don’t Repeat Yourself!
• Keep It Simple, Stupid!
• the less code you write, the more
maintainable and ﬂexible your app is
• you don’t have to ship your product to
your customers - show it, get feedback,
make it better, deploy a new version, get
most of the things are
done for you.
• data, time zones
• CSRF attacks
• ...and many more.
developer’s tools for...
• maintaining code
• monitoring your production application
• blogs, wiki, railscasts, podcasts, e-books,
traditional books, irc channels, discussion
• it’s a great thing. really.
The Rails Myths: Rails
• ...is hard to deploy
• ...is hard because of ruby
• ...only speaks english
Rails is hard to deploy
• Phusion Passenger
• hosting Rails in Poland? no longer a pain in
Rails is hard because of
• just try it yourself.
• it takes as much time as it would to learn a
framework in language that you already
• and then things go faster. and they are
easier. and prettier. and better. believe me.
Rails only speaks
• time zones
downsides of rails?
• convention over conﬁguration
• it’s harder to satisfy geeks and power users