Browse files

Generated pages

  • Loading branch information...
1 parent 4986af4 commit 23533b067c30f9cbe4476f264fde5362607bfdaf @benjaminoakes benjaminoakes committed Apr 23, 2012
Showing with 1,477 additions and 4 deletions.
  1. +16 −0 Aaron-Patterson-Keynote.md
  2. +16 −0 ActiveRecord-Scopes-and-Arel.md
  3. +16 −0 ActiveSupport-and-ActiveModel.md
  4. +32 −0 Basecamp-Next:-Code-Spelunking.md
  5. +16 −0 Basic-Rake.md
  6. +20 −0 COOKPAD-Keynote.md
  7. +24 −0 ...-multiple-feature-prototypes-in-production-for-test-segments-of-their-15-million-engaged-users.md
  8. +28 −0 CoffeeScript-for-the-Rubyist.md
  9. +24 −0 Complex-Made-Simple:-Sleep-Better-with-TorqueBox.md
  10. +18 −0 David-Cohen-Keynote.md
  11. +17 −4 David-Heinemeier-Hansson-keynote.md
  12. +24 −0 Deconstructing-Travis.md
  13. +22 −0 Designing-Hypermedia-APIs.md
  14. +28 −0 Digging-Deep-with-ActiveSupport::Notifications.md
  15. +20 −0 Evented-Ruby-vs-Node.js.md
  16. +22 −0 Extending-Ruby-with-Ruby.md
  17. +24 −0 From-Rails-Rumble-to-50,000,000-results.md
  18. +26 −0 Getting-Down-To-Earth:-Geospatial-Analysis-With-Rails.md
  19. +16 −0 How-to-Find-Valuable-Gems.md
  20. +8 −0 Ignite-RailsConf.md
  21. +16 −0 Introduction-to-RSpec.md
  22. +20 −0 Its-Not-in-Production-Unless-its-Monitored.md
  23. +28 −0 Keeping-Rails-Applications-on-Track-with-Brakeman.md
  24. +18 −0 KidsRuby.md
  25. +24 −0 Let's-make-the-web-faster-tips-from-trenches-@-Google.md
  26. +28 −0 Lightning-Talks.md
  27. +20 −0 MiniTest:-Refactoring-Test-Unit-and-RSpec-back-to-version-0.0.1.md
  28. +26 −0 Mobile-Rage-What-causes-it-how-to-fix-it.md
  29. +28 −0 Patella:-It's-Memoization-into-Memcached-calculated-in-the-background-with-Resque..md
  30. +16 −0 Powerful-Interfaces.md
  31. +22 −0 Practical-Machine-Learning-and-Rails.md
  32. +26 −0 Presenters-and-Decorators:-A-Code-Tour.md
  33. +20 −0 Progressive-Enhancement-on-the-Mobile-Web.md
  34. +16 −0 RVM-Essential-Rails-Development-Tools.md
  35. +31 −0 Rails-Engines-Patterns.md
  36. +24 −0 Rails-Testing-for-Zombies.md
  37. +23 −0 Rails-for-Zombies-(AKA-Intro-to-Rails-Part-1).md
  38. +23 −0 Rails-for-Zombies-2-(AKA-Intro-to-Rails-Part-2).md
  39. +30 −0 Rails:-The-Next-Five-Years.md
  40. +16 −0 Railsflavored-Ruby.md
  41. +32 −0 Realtime-web-applications-with-streaming-REST.md
  42. +31 −0 Redis-Application-Patterns-in-Rails.md
  43. +16 −0 Rich-Hickey-Keynote.md
  44. +31 −0 RoRoRoomba-Ruby-on-Rails-on-Roomba.md
  45. +20 −0 Ruby-Hero-Awards-Keynote.md
  46. +33 −0 Ruby-Rogues-Live-Keynote.md
  47. +30 −0 Sand-Piles-and-Software.md
  48. +26 −0 Schemaless-SQL-The-Best-of-Both-Worlds.md
  49. +16 −0 Securing-the-Rails.md
  50. +26 −0 Securing-your-site.md
  51. +22 −0 Semi-Automatic-Code-Review.md
  52. +34 −0 Stack-Smashing.md
  53. +20 −0 Sustainable-Productivity-with-Rails.md
  54. +45 −0 Taming-the-Kraken-How-Operations-enables-developer-productivity.md
  55. +24 −0 Ten-Things-You-Didn't-Know-Rails-Could-Do.md
  56. +16 −0 Testing-Best-Practices,-or-The-Five-Habits-of-Highly-Effective-Tests.md
  57. +21 −0 The-Future-of-Sass.md
  58. +22 −0 Use-the-Source,-Luke:-High-fidelity-data-with-event-sourcing.md
  59. +22 −0 Using-Backbone.js-with-Rails:-Patterns-from-the-Wild.md
  60. +24 −0 Using-Rails-without-Rails.md
  61. +16 −0 Welcome-Keynote.md
  62. +34 −0 What-a-long-Strange-Trip-it-has-been..md
  63. +24 −0 Zero-downtime-deploys-for-Rails-apps.md
  64. +20 −0 i18n-on-Rails:-A-Twitter-Approach.md
View
16 Aaron-Patterson-Keynote.md
@@ -0,0 +1,16 @@
+**Presenter:** Aaron Patterson
+
+## Abstract
+
+> When he isn't ruining people's lives by writing software like phuby, enterprise, and neversaydie, Aaron can be found writing slightly more useful software like nokogiri. To keep up his Gameboy Lifestyle, Aaron spends his weekdays writing high quality software for ATTi. Be sure to catch him on Karaoke night, where you can watch him sing his favorite smooth rock hits of the 70's and early 80's.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 ActiveRecord-Scopes-and-Arel.md
@@ -0,0 +1,16 @@
+**Presenter:** Jacob Swanner
+
+## Abstract
+
+> Scopes are a great way of encapsulating query logic in a granular, reusable way. This talk will cover some techniques you can use to keep those scopes as composable and portable as possible. We’ll cover how to use Arel directly, while avoiding the common practice of using SQL fragments, and show you how this can make your scopes more reusable, while at the same time preventing you from using database vendor specific operators, such as ILIKE.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 ActiveSupport-and-ActiveModel.md
@@ -0,0 +1,16 @@
+**Presenter:** Bryan Liles
+
+## Abstract
+
+> Have you ever wondered what makes Rails tick? Bryan Liles will cover two of the pillars of the Rails foundation: ActiveSupport and ActiveModel. Together we will discover where some of Rails’ ease and power originates and how make use of it in your projects.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
32 Basecamp-Next:-Code-Spelunking.md
@@ -0,0 +1,32 @@
+**Presenter:** Nick Quaranto
+
+## Bio
+
+> Programmer at 37signals, Husband, Husky wrangler, RIT Alum, http://rubygems.org Mechanic.
+
+## Abstract
+
+> Heard about the big Basecamp launch this March? Wondering what's new, how it's shaping Rails, and the tech behind it? We're going to go over some the practices and patterns in the new Basecamp's code base and you can learn how to improve your app with them.
+>
+> Some of what we'll go over:
+>
+> * Employing concerns to share code across models/controllers
+> * Stacker, the CoffeeScript component behind the "page" based layout
+> * Why polling for updates still works at scale
+> * Client side testing without the hassle
+> * Using jbuilder to keep view data out of models
+> * Keeping your team's sanity with a single setup script
+> * Debugging painful JavaScript performance slowdowns
+> * How to keep your app alive even if external dependencies like Redis are down
+> * Why tagged request logging and action/controller SQL query logging can make finding bugs easier
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 Basic-Rake.md
@@ -0,0 +1,16 @@
+**Presenter:** Jim Weirich
+
+## Abstract
+
+> Anyone who develops with Rails uses the Rake tool all the time. Rake will run your tests, migrate your database, and precompile your assets. But did you know you can define and build your own Rake tasks? This short talk will cover the basics of using Rake and writing simple automation tasks to make your development process smother.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
20 COOKPAD-Keynote.md
@@ -0,0 +1,20 @@
+**Presenter:** COOKPAD
+
+## Bio
+
+> Thank you to the Rails community, from Cookpad and 15 million families.
+
+## Abstract
+
+> TBD
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
24 ...e-feature-prototypes-in-production-for-test-segments-of-their-15-million-engaged-users.md
@@ -0,0 +1,24 @@
+**Presenter:** Kenta Murata
+
+## Bio
+
+> Kenta Murata is an Engineer at Cookpad in Tokyo, Japan. He is also a Ruby committer maintaining the bigdecimal library.
+
+## Abstract
+
+> Chanko provides a simple framework for rapidly and safely prototyping new features in your production Rails app, and exposing these prototypes to specified segments of your user base.
+>
+> With Chanko, you can release many concurrent features and independently manage which users see them. If there are errors with any chanko, it will be automatially removed, without impacting your site.
+>
+> Chanko was extracted from Cookpad.com where the team uses it daily to test new features live, in production, on the largest Rails site in Japan which serves 500 million page views a month to a user based of over 15 million highly engaged uses.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
28 CoffeeScript-for-the-Rubyist.md
@@ -0,0 +1,28 @@
+**Presenter:** Mark Bates
+
+## Bio
+
+> Mark Bates is the founder and chief architect of the Boston, MA based consulting company, Meta42 Labs. Mark spends his days focusing on new application development and consulting for his clients. At night he writes books, raises kids, and occasionally he forms a band and “tries to make it”.
+>
+> Mark has been writing web applications, in one form or another, since 1996. His career starting as a UI developer writing HTML and JavaScript applications before moving towards the middle(ware) with Java and Ruby.
+>
+> Always wanting to share his wisdom, or more correctly just wanting to hear the sound of his own voice, Mark has spoken at several high profile conferences, include RubyConf and jQueryConf. Mark has also taught classes on Ruby and Ruby on Rails. In 2009 Mark’s first (surprisingly not his last!) book, “Distributed Programming with Ruby”, was published by Addison-Wesley. In 2012 Addison-Wesley published Mark’s second book, “Programming in CoffeeScript”.
+>
+> Mark lives just outside of Boston with his wife Rachel and their two sons, Dylan and Leo. Mark can be found on the web at: http://www.markbates.com, http://twitter.com/markbates, and http://github.com/markbates
+
+## Abstract
+
+> CoffeeScript is taking the world, and particularly the Rails eco system, by storm. This little language has provided an almost Ruby like abstraction onto of JavaScript. CoffeeScript is trying to make writing front end code as much fun as Ruby makes writing backend code.
+>
+> In this talk we start with the basic concepts of CoffeeScript and move on to the more powerful and fun features of the language. While we're looking at CoffeeScript we'll see how it relates to the Ruby code we write everyday. What do Ruby 1.9 lambdas and CoffeeScript functions have in common? Which of the two languages supports splats, default arguments, and ranges? The answers may surprise you.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
24 Complex-Made-Simple:-Sleep-Better-with-TorqueBox.md
@@ -0,0 +1,24 @@
+**Presenter:** Lance Ball
+
+## Bio
+
+> Lance Ball is a Senior Software Developer at Red Hat and a core member of the TorqueBox team. He has been writing code for over a dozen years in startups, as a consultant, and working for The Man. His ideas have been expressed in Ruby, Java, Perl and C++. As a consultant, Lance wrote Rails and Sinatra applications before joining Red Hat. He's on Twitter as @lanceball.
+
+## Abstract
+
+> Even the simplest of Rails applications can eventually grow into a twisted mess of complexity. At some point you will need a background task, or a long-running service, or a scheduled job, or all of the above and more. All of these little bits of functionality added to an application ad hoc can keep you up at night with cold sweats and nightmares. But it doesn't have to be that way.
+>
+> In this presentation, we will examine a complex Rails application - complexity that is eventually common to most modern Rails apps: background tasks, scheduled jobs, WebSockets, long-running services, caching and more. We will look at the challenges inherent in these features for both development and deployment. Then we'll look to TorqueBox for simple solutions to these complex problems. You'll never have that long-runing service using the wrong Ruby code again; no more environment variable nightmares in your cron jobs. You can sleep better now.
+>
+> TorqueBox is a Ruby application server that is built on JRuby and JBoss AS7. It provides asynchronous messaging, scheduled jobs, long-running processes, caching, simple deployment, and much more. TorqueBox is designed to bring the power, scalability and stability of these time-tested JavaEE services to Ruby applications through a simple and expressive Ruby interface.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
18 David-Cohen-Keynote.md
@@ -0,0 +1,18 @@
+**Presenter:** David Cohen
+
+## Abstract
+
+> David Cohen is the founder and CEO of TechStars. Previously, David was a founder of several software and web technology companies. He was the founder and CTO of Pinpoint Technologies which was acquired by <a href="http://www.zoll.com/">ZOLL Medical Corporation</a> (NASDAQ: <a href="http://quotes.nasdaq.com/asp/summaryquote.asp?symbol=ZOLL%60&amp;selected=ZOLL%60">ZOLL</a>) in 1999. You can read about it in <a href="http://www.amazon.com/gp/product/1420819917/sr=8-1/qid=1141840409/ref=sr_1_1/103-1943388-3567068?%5Fencoding=UTF8">No Vision, All Drive</a> [Amazon]. David was also the founder and CEO of <a href="http://www.askdavetaylor.com/keep_track_of_my_favorite_musicians.html">earFeeder.com</a>, a music service which was sold to <a href="http://www.sonicswap.com/">SonicSwap.com</a> in 2006. He also had what he likes to think of as a "<a href="http://www.davidgcohen.com/2006/11/22/life-in-the-deadpool/">graceful failure</a>" in between.
+>
+> David is a active startup advocate, advisor, board member, and technology advisor who comments on these topics on his blog at <a href="http://www.davidgcohen.com/">DavidGCohen.com</a>. He recently co-authored <a href="http://domorefasterbook.com/"><em>Do More Faster</em></a> with Brad Feld. He is also very active at the <a href="http://www.colorado.edu/">University of Colorado</a>, serving as a member of the Board of Advisors of the <a href="http://www.cs.colorado.edu/">Computer Science Department</a>, the <a href="http://www.silicon-flatirons.org/people.php?id=EntrepreneurialBoardMember">Entrepreneurial Advisory Board at Silicon Flatirons</a>, and the Board of Advisors of the <a href="http://leeds.colorado.edu/Deming/interior.aspx?id=548">Deming Center</a> Venture Fund. He is a member of the selection committee for <a href="http://www.vcintherockies.com/">Venture Capital in the Rockies</a>, and runs the Colorado chapter of the <a href="http://www.openangelforum.com/">Open Angel Forum</a>. His hobbies are technology, software/web startups, business history, and tennis. He is married to the <a href="http://www.jilato.com/">coolest girl</a> he's ever met and has three amazing kids who always seem to be teaching him something new.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
21 David-Heinemeier-Hansson-keynote.md
@@ -1,7 +1,20 @@
-**Presenter:** [@dhh](http://twitter.com/dhh)
+**Presenter:** David Heinemeier Hansson
-> David Heinemeier Hansson is a partner at 37signals, a privately-held Chicago-based company committed to building the best web-based tools possible with the least number of features necessary.
->
+## Abstract
+
+> David Heinemeier Hansson is a partner at <a href="http://37signals.com/">37signals</a>, a privately-held Chicago-based company committed to building the best web-based tools possible with the least number of features necessary.
+>
> 37signals' products include Basecamp, Highrise, Backpack, Campfire, Ta-da List, and Writeboard. 37signals' products do less than the competition -- intentionally.
->
+>
> He is also the creator of Ruby on Rails.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
24 Deconstructing-Travis.md
@@ -0,0 +1,24 @@
+**Presenter:** Josh Kalderimis
+
+## Bio
+
+> Josh is a top 30 Ruby on Rails contributor and has been working with the framework since 2008. He maintains a bunch of open-source Ruby projects, including multi_json, linkedin, faraday_middleware and his own completeness-fu. He's also one of Amsterdam.rb's organizers, and an integral part of the core Travis-CI team.
+
+## Abstract
+
+> Unless you have been living under a rock for the past year you might know of Travis CI, the continuous integration service for the open source community.
+>
+> Travis started as a single GitHub project which was a rails app and a resque background task. Compare that to 12 months later where Travis is now four separate deployable apps, uses two different rubies (1.9.2 and jruby), and comprises a total of 10 GitHub projects.
+>
+> Apart from looking at how Travis works now, we will also look at how it got there, and how we broke Travis up into smaller more manageable, more concise encapsulated services.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
22 Designing-Hypermedia-APIs.md
@@ -0,0 +1,22 @@
+**Presenter:** Steve Klabnik
+
+## Bio
+
+> Steve is a Ruby Hero, software craftsman, and an aspiring digital humanities scholar. He spends most of his time contributing to Open Source projects, and maintains both Hackety Hack and Shoes. He also teaches classes with Jumpstart Lab.
+
+## Abstract
+
+> Rails did a lot to bring REST to developers, but its conception leaves the REST devotee feeling a bit empty. "Where's the hypermedia?" she says. "REST isn't RPC," he may cry. "WTF??!?!" you may think. "I have it right there! resources :posts ! What more is there? RPC? Huh?"
+>
+> In this talk, Steve will explain how to design your APIs so that they truly embrace the web and HTTP. Just as there's an impedance mismatch between our databases, our ORMs, and our models, there's an equal mismatch between our applications, our APIs, and our clients. Pros and cons of this approach will be discussed, as well as why we aren't building things this way yet.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
28 Digging-Deep-with-ActiveSupport::Notifications.md
@@ -0,0 +1,28 @@
+**Presenter:** Matt Sanders
+
+## Bio
+
+> Matt Sanders (@nextmat) is a Senior Software Engineer at Librato, Inc, where he works on the Metrics real-time monitoring platform and dreams of making your data beautiful. He’s been active in the Ruby community since 2005 and is a regular contributor to open-source projects including compass-960 and excon. On sunny days he can be found chasing waves on the Texas coast.
+
+## Abstract
+
+> Rails 3 and above includes a powerful instrumentation system, ActiveSupport::Notifications, which can be used to track performance and event information for all aspects of your application. Notifications are light-weight, easy to setup, and can be consumed by multiple subscribers (logs, audit trails, consolidated metrics, other parts of your application).
+>
+> In this session we’ll start with the basics of ActiveSupport::Notifications and work our way to powerful advanced use cases. Topics we’ll explore include:
+>
+> - How to set up and use notifications
+> - Logging what you want from any tier of your system
+> - How to capture and aggregate performance/business data for the metrics you care about most
+> - Conditional monitoring in production: flag on and off data by system or customer to get to the root of problems more quickly
+> - Using ActiveSupport::Notifications in non-Rails applications and your own libraries
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
20 Evented-Ruby-vs-Node.js.md
@@ -0,0 +1,20 @@
+**Presenter:** Jerry Cheung
+
+## Bio
+
+> Jerry Cheung splits his time as a co-founder of Opperator and a developer at Intridea. He is a co-author of the upcoming MacRuby in Action, and likes contributing to open source. He's currently dabbling in evented Ruby and Grape driven webapps. When he's not coding, he stalks awesome cars in Southern California and writes about them in RockyRoadBlog.
+
+## Abstract
+
+> While Node.js is the hot new kid on the block, evented libraries like EventMachine for Ruby and Twisted for Python have existed for a long time. When does it make sense to use one over the other? What are the advantages and disadvantages to using node over ruby? In this talk, you will learn how to get the same power of concurrency enjoyed by Node.js while continuing to write in the language you know and love. Topics covered will include pubsub with redis or faye, building evented rack applications, and running evented applications alongside existing Rails apps.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
22 Extending-Ruby-with-Ruby.md
@@ -0,0 +1,22 @@
+**Presenter:** Michael Fairley
+
+## Bio
+
+> Michael Fairley (@michaelfairley) is the lead developer at 1000memories, where he helps people preserve and cherish their most valuable memories. He’s an active open source contributor, and maintains a handful of side projects including mincemeat.py and bestintrobook.com.
+
+## Abstract
+
+> Other programming languages have powerful features that are often enviable while working in Ruby: Python’s function decorators, Scala’s partial evaluation, and Haskell’s lazy evaluation, among others. Fortunately, Ruby’s metaprogramming facilities give us the ability to add these features to Ruby ourselves, without the need for the core language to be changed.
+>
+> This talk will walk through adding simple (yet functional) versions of the previously mentioned features to Ruby, using Ruby, and discuss the dos and don’ts of responsible Ruby metaprogramming.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
24 From-Rails-Rumble-to-50,000,000-results.md
@@ -0,0 +1,24 @@
+**Presenter:** Mikel Lindsaar
+
+## Bio
+
+> Mikel Lindsaar heads up reInteractive, a Rails development company in Sydney Australia and StillAlive.com a web application monitoring service, he is also the author of the Ruby mail gem, is on the Rails commit team for his work on ActionMailer and has contributed to many open source projects.
+
+## Abstract
+
+> StillAlive.com was born from the 48 hour intense 2010 Rails Rumble and has grown! Having recently passed our 50,000,000th site result, this talk discusses the real world challenges and optimisations required to take a code base born from the fires of YAGNI to a production system.
+>
+> This talk isn't about how you can scale from 0 requests to 500 billion requests per microsecond, but give a practical view to some of the performance problems we faced as the application steadily grew from a hack job into a functioning system.
+>
+> The journey will go through the mistakes we made, challenges faced and real world optimisations discovered, including some tricks we learnt along the way from concurrent index creation to using the ZeroMQ messaging framework with Rails
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
26 Getting-Down-To-Earth:-Geospatial-Analysis-With-Rails.md
@@ -0,0 +1,26 @@
+**Presenter:** Daniel Azuma
+
+## Bio
+
+> Daniel Azuma is a Ruby developer specializing in geospatial technologies, computational geometry, graphics, and related fields. He is the author of RGeo and related gems commonly used for geospatial analysis in Ruby and Rails applications. He currently works as Chief Software Architect at Pirq, and blogs at daniel-azuma.com.
+
+## Abstract
+
+> It is no secret that location has become ubiquitous. Mobile GPS, available data sets, and easy-to-use mapping services have brought geospatial information within reach of web developers. Location already plays a significant role in many of the major services such as Twitter, Facebook, and Google, not to mention legions of startups.
+>
+> However, for those of us implementing more than the most trivial features, it is also true that location is challenging. A significant learning curve awaits us, involving spatial databases, coordinate systems, interchange formats, and plenty of math. Our Ruby-based tools lag a bit behind those available to our Java- and Python-oriented colleagues, and effective documentation is scarce.
+>
+> This presentation aims to jump-start Rails developers hoping to go beyond putting a few pushpins on a Google Map. Rather than spending a lot of time explaining the many concepts involved, we'll bypass the learning curve and jump straight into walking through code for a few nontrivial applications. The hope is that the conceptual knowledge will come naturally as a result of seeing it in action, but pointers to online resources will also be provided to fill in any gaps.
+>
+> A thorough understanding of Ruby, Rails, ActiveRecord, and SQL will be assumed. No prior knowledge of GIS or computational geometry will be required, though it may be helpful.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 How-to-Find-Valuable-Gems.md
@@ -0,0 +1,16 @@
+**Presenter:** Nathaniel Bibler
+
+## Abstract
+
+> There’s no need to reinvent the wheel. There are over 30,000 RubyGems available on just RubyGems.org, alone. But with so many out there, it must be impossible to find the right one, right? In this talk we’ll learn about some resources which help you find the right gems, as well as how to intelligently decide if a library is right for your project.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
8 Ignite-RailsConf.md
@@ -1,3 +1,11 @@
+**Presenter:** Ignite RailsConf
+
+## Bio
+
+> Five minutes, 20 slides. What would you say? Sixteen artists, technologists, thinkers, and personalities take the stage to answer this challenge. What is Ignite? Fast-paced, fun, thought-provoking, social, local, global - Ignite is all of these and more. It's a high-energy evening of 5-minute talks by people who have an idea - and the guts to get onstage and share it with the rest of the Rails community.
+
+## Notes
+
From [here](http://railsconf.austinonrails.org/ignite).
> Five minutes, 20 slides. What would you say? Sixteen artists, technologists, thinkers, and personalities take the stage to answer this challenge. What is Ignite? Fast-paced, fun, thought-provoking, social, local, global - Ignite is all of these and more. It's a high-energy evening of 5-minute talks by people who have an idea - and the guts to get onstage and share it with the rest of the Rails community. We're looking for a wide range of talks and are currently accepting speaking proposals - submit your speaking proposal now! Not all of the talks will be Rails-specific but all will be of interest to Rails developers. You do not have to be a RailsConf attendee to attend or speak at the event. Proposals were due by 5 pm CT on Friday, 4/13/2012.
View
16 Introduction-to-RSpec.md
@@ -0,0 +1,16 @@
+**Presenter:** Jon &quot;Lark&quot; Larkowski
+
+## Abstract
+
+> “A testing tool by any other other name would assert as truthy.” – some guy. You’ve seen Rails’ built-in Test::Unit in the morning session. This afternoon, we’ll introduce RSpec, another popular testing tool. We’ll overview basic structure, contexts, “should” expectations, mocking and stubbing. We’ll also cover Rails model, view, controller, routing, helper, and request specs.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
20 Its-Not-in-Production-Unless-its-Monitored.md
@@ -0,0 +1,20 @@
+**Presenter:** Joseph Ruscio
+
+## Bio
+
+> Joseph Ruscio is a Co-Founder and CTO at Librato, Inc. He’s responsible for the company’s technical strategy, architecture, and generally hacks on all levels of the product. He’s a Ruby enthusiast and the author of the aggregate and rack-test-rest gems. @josephruscio on Twitter and Github.
+
+## Abstract
+
+> In the 21st century successful teams are data-driven. We’ll present a complete introduction to everything you need to start monitoring your service at every level from business drivers to per-request metrics in Rails/Rack, down to server memory/cpu. Provides a high-level overview of the fundamental components that comprise a holistic monitoring system and then drills into real-world examples with tools like ActiveSupport::Notifications, statsd/rack-statsd, and CollectD. Also covers best practices for active alerting on custom monitoring data.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
28 Keeping-Rails-Applications-on-Track-with-Brakeman.md
@@ -0,0 +1,28 @@
+**Presenter:** Justin Collins
+
+## Bio
+
+> Justin is a Ph.D. candidate at UCLA and currently works as an application security engineer at Twitter.
+
+## Abstract
+
+> A recent report by Veracode (http://www.veracode.com/reports/index.html) found cross-site scripting in 68% of surveyed web applications and SQL injection in 32%, even though these are well-known, easily preventable, and easily detectable vulnerabilities. As applications grow larger, it becomes harder and harder to manually verify that every line of code is adhering to security guidelines - even given the built-in protection available with Ruby on Rails.
+>
+> Brakeman (http://brakemanscanner.org/) is an open source static analysis tool which provides painless vulnerability scans of Rails code from "rails new" through deployment. Running Brakeman as a part of continuous integration provides feedback during all stages of development and can alert developers immediately when a potential vulnerability is introduced. Bringing security testing as close to the developer as possible (even scanning as files are saved) means security problems are caught faster - and the sooner problems are found the cheaper they are to fix.
+>
+> As a static analysis tool, Brakeman can be run without worrying about deploying the whole application stack: no webserver, database, configuration, or application dependencies required - not even Rails itself. This allows fast, easy vulnerability scans on any Rails project.
+>
+> We talk a lot about testing in the Ruby and Rails community, but somehow security testing is passed over. This needs to change!
+>
+> This talk will cover how to incorporate Brakeman into Rails development and how it can improve application security, as well as a look into how Brakeman works internally.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
18 KidsRuby.md
@@ -0,0 +1,18 @@
+**Presenter:** KidsRuby
+
+## Bio
+
+> Did you ever want to make a videogame, program a robot, or create a web site? Now you can!
+>
+> Come to KidsCodeCamp, a free one-day event to learn how to use computers and technology to make things that do whatever you want.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
24 Let's-make-the-web-faster-tips-from-trenches-@-Google.md
@@ -0,0 +1,24 @@
+**Presenter:** Ilya Grigorik
+
+## Bio
+
+> Ilya Grigorik is a web performance engineer, an open-source and Ruby evangelist, a data geek, and a proverbial early adopter of all things digital. He is currently helping lead the social analytics and web performance efforts at Google. Earlier, Ilya was the founder and CTO of PostRank, a social analytics company, which was acquired by Google.
+
+## Abstract
+
+> Google loves speed, and we want to make the entire web faster - yes, that includes your Rails app! We'll explore what we've learned from running our own services at scale, as well as cover the research, projects, and open sourced tools we've developed in the process.
+>
+> We'll start at the top with website optimization best practices, take a look at what the browser and HTML5 can do for us, take a detour into the optimizations for the mobile web, and finally dive deep into the SPDY and TCP protocol optimizations.
+>
+> We'll cover a lot of ground, so bring a coffee. By the end of the session, you should have a good checklist to help you optimize your own site.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
28 Lightning-Talks.md
@@ -0,0 +1,28 @@
+**Presenter:** Dr Nic Williams
+
+## Bio
+
+> Dr Nic is a developer’s developer.
+>
+> He writes blog posts for developers; creates tools, libraries and text editor extensions for developers; and speaks to developers at conferences.
+>
+> He’s the VP of Developer Evangelism at Engine Yard, the premier platform as a service.
+>
+> He’s Australian and now living in the Bay Area.
+>
+> And he’s funny; if you can understand his accent.
+
+## Abstract
+
+> You know 'em, you love 'em -- five-minute talks by attendees on topics that they're passionate about. We'll have a signup sheet available from the start of the conference, so start thinking of ideas today!
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
20 MiniTest:-Refactoring-Test-Unit-and-RSpec-back-to-version-0.0.1.md
@@ -0,0 +1,20 @@
+**Presenter:** Jared Ning
+
+## Bio
+
+> Jared Ning is a freelancer from Oklahoma City. Since becoming a freelancer a year and half ago, he has been living according to the philosophy "red, green, travel until the money runs out, repeat".
+
+## Abstract
+
+> MiniTest is the no-nonsense testing framework you already know how to use. If we strive for cleaner and simpler code in our own work, wouldn't it be nice to have that in our test framework too? Whether you're a Test Unit fan or RSpec fan, you'll feel right at home using MiniTest. Its simplicity makes it fast, easy to use, extendable, and maybe most importantly, easy to understand. Plus, Rails 4 uses MiniTest.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
26 Mobile-Rage-What-causes-it-how-to-fix-it.md
@@ -0,0 +1,26 @@
+**Presenter:** Lori M Olson
+
+## Bio
+
+> Six years ago Lori tried Ruby/Rails as an alternative to Java development and "has never looked back!" She has been delivering Rails and Javascript based applications in the oil & gas industry for the last six years, working for companies like Labrador Technologies, CodeGear/Borland, and Intellog.
+>
+> Lori has a long list of speaking credits. Most recently, she spoke at Confoo 2012 in Montreal, jQuery Conf Boston 2011, Madison Ruby 2011, and Conferencia Rails 2010 in Madrid. She has also presented at the CodeRage and COSSFEST conferences, and has presented frequently to the Calgary Ruby User Society, of which she is also a co-founder
+
+## Abstract
+
+> Most of us have been there. That website you want to use, from your mobile device, that just refuses to cooperate. From the Flash-only, to the can't f**king log in, to the redirect-to-mobile-and-stay-there sites, there's more than enough websites out there to invoke Mobile Rage.
+>
+> Although we all know that the best mobile development strategy is "mobile-first", we also all know how many sites and applications out there were designed and built by people who didn't imagine how fast mobile would take over.
+>
+> Come learn about the common mistakes most people make for mobile, and some of the simple solutions you can use to help reduce Mobile Rage, without having to do a complete rewrite.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
28 Patella:-It's-Memoization-into-Memcached-calculated-in-the-background-with-Resque..md
@@ -0,0 +1,28 @@
+**Presenter:** Jeff Dwyer
+
+## Bio
+
+> Jeff Dwyer is a Sr Software Engineer at PatientsLikeMe. He's the author of the book Pro Web 2.0 with GWT and he will buy you a drink if you tell him you've read it. Even if you're lying. Once upon a time he taught GWT at conferences from Las Vegas to Prague. If you delayed your flight from Java to Ruby because you were enthralled by one of these talks he will buy you two drinks. Jeff is a father of two and lives in Hanover, NH.
+
+## Abstract
+
+> I regularly write code that does something great but is slow as a dog. Denormalizing / pre-computing / backgrounding are all fine, but they're all an investment and they leave tentacles all through the code. I want to be able to try out slow but very useful code in my app without the friction of performance concerns, but also without worrying that my ops engineer is going to kill me in my sleep.
+>
+> Wouldn't it be nice to add one line to our models that takes care of caching, cache keys, backgrounding, dog-piling, and cache warming? Oh, and it should give the UI clear consistent hooks so that it's clear whether the data is ready so the UI can render a spinner or disable a feature until the computation is complete.
+>
+> We'll take a look at a series of techniques that we use at PatientsLikeMe to allow us to safely and quickly put some very expensive queries on the website so that we can evaluate whether it's worthwhile to create longer term solutions. The solution we've come up with is a lot of gloss over memcache and resque that makes it feel like we can memoize any method in our application and lets us focus on the goals of the algorithms rather than their performance and architecture.
+>
+> This talk will feature: memcache, resque, a bit of metaprogramming, a look at caching in the wild and code that fixes some usual problems, and a fairly epic SQL query with some nice Postgres features you should know about.
+>
+> You should come if: you want to take a look at some practical solutions that we use in production to be able to roll out computationally expensive features.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 Powerful-Interfaces.md
@@ -0,0 +1,16 @@
+**Presenter:** Caike Souza
+
+## Abstract
+
+> In this talk we will explore the best practices in using interfaces as the foundation for designing object oriented applications in Ruby and Rails. We will talk about some of the techniques that make it possible to write loosely coupled components that can be easily extended to respond to requirement changes.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
22 Practical-Machine-Learning-and-Rails.md
@@ -0,0 +1,22 @@
+**Presenter:** Andrew Cantino &amp; Ryan Stout
+
+## Bio
+
+> Andrew Cantino has been building web applications for over fifteen years. Andrew has a Masters in Computer Science from Georgia Tech, where he focused on machine learning and artificial intelligence. He has worked on Gmail at Google, on video search at CastTV, and recently spent two years practicing Agile software development at Pivotal Labs. Andrew is currently VP of Engineering at Mavenlink.
+>
+> Ryan Stout has also been doing web development for fifteen years and has been working with Rails for the last six. He runs a small web-consulting agency and has been involved in startups ranging from social gaming to online dating and domain search. He spent the last year developing a stealth startup that uses both natural language processing systems and modern machine learning techniques.
+
+## Abstract
+
+> Many people know that machine learning techniques can facilitate learning from, and adapting to, noisy, real-world data, but aren't sure how to begin using them. Starting with two real-world examples, we will introduce you to some libraries that bring machine learning techniques to your Rails applications. We will then dive into the art of feature design, one of the first practical roadblocks that many people encounter when applying machine learning. Feature design is the challenging, subtle, and often trail-and-error process of selecting and transforming the data you provide for your learning algorithm, and it is often the hardest part of using these techniques. Our goal is for you to come out of this talk with the tools necessary to think about machine learning and how to apply it to your problems.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
26 Presenters-and-Decorators:-A-Code-Tour.md
@@ -0,0 +1,26 @@
+**Presenter:** Mike Moore
+
+## Bio
+
+> Mike Moore hacks for a living at Bloomfire. He organizes conferences, is an occasional podcaster, part-time purveyor of Ruby-themed apparel, and tries to be a nice guy. He loves his family and the Ruby community.
+>
+> http://blowmage.com/
+> http://twitter.com/blowmage
+> http://github.com/blowmage
+
+## Abstract
+
+> Presenter and Decorators are design approaches that can be used in Rails applications outside of the standard Models, Views and Controllers. These approaches are becoming more and more popular as teams search for new ways to identify and manage the complexity within their applications.
+>
+> In this session Mike Moore will defined the Presenter and Decorator approaches using simple and clear terminology. Common design problems in Rails applications will be shown using real-life code examples and refactored toward Presenters and Decorators. Code will be improved and strengthened by identifying and respecting the dependencies within large applications.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
20 Progressive-Enhancement-on-the-Mobile-Web.md
@@ -0,0 +1,20 @@
+**Presenter:** John Bender
+
+## Bio
+
+> John Bender is the co-creator of Vagrant, a jQuery Mobile contributor, and a recovering polygot. During the day he works full-time on jQuery Mobile at Adobe and otherwise spends his time hacking on open source. John shares his thoughts at http://johnbender.us and as @johnbender on Twitter.
+
+## Abstract
+
+> Progressive Enhancement isn't important on the mobile web because it's all Webkit right? Not so fast. Even among Webkit implementations events, css, and performance vary widely. We'll talk about the darker corners of the mobile web and show how jQuery Mobile can help you build Rails applications that are reliable, accessible, and support more devices.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 RVM-Essential-Rails-Development-Tools.md
@@ -0,0 +1,16 @@
+**Presenter:** Olivier Lacan
+
+## Abstract
+
+> Working with Rails often means switching between several Ruby versions back and forth which is made almost seamless by RVM. It also involves several simple command line tools like Pry, Guard, and Pow and that will make your development life so much easier.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
31 Rails-Engines-Patterns.md
@@ -0,0 +1,31 @@
+**Presenter:** Andy Maleh
+
+## Bio
+
+> Andy Maleh is a Software Engineer at Groupon who specializes in user needs analysis and building transformative software that meets ongoing demands. He leads by embracing agile practices and software craftsmanship in the process of perfecting Groupon's deal experience. He joined Groupon via Obtiva, where he served as a Senior Consultant for more than five years. Andy is also the Founder and Lead Developer of the Glimmer open source project for Desktop Development with Ruby.
+>
+> Andy holds an M.S. in Software Engineering from DePaul University in Chicago and a B.S. in Computer Science from McGill University (Montreal). Outside of Groupon walls, Andy is a drummer in two indie rock bands (Gag Order and Cletus Darby) and travels via Longboard when the Chicago weather permits.
+
+## Abstract
+
+> This talk covers a successful utilization of Rails Engines to share features that cut across the layers of MVC in different Rails 3 projects. Rails Engines thus provide the best of both worlds: improved productivity by reusing MVC code (including assets like Javascript, CSS, and Images) and better flexibility by allowing different applications to customize behavior as needed without reliance on application-dependent conditionals. Rails Engine patterns will be provided to guide developers on how to leverage Rails Engines' reusability and flexibility without sacrificing maintainability.
+>
+> Outline:
+>
+> - Basics of Rails Engines
+> - Rails Engine Patterns
+> - Improved Productivity Tips
+> - Summary of Benefits and Trade-Offs
+>
+> Attendees should walk away with an overview of Rails Engines and guidelines on how to utilize them effectively.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
24 Rails-Testing-for-Zombies.md
@@ -0,0 +1,24 @@
+**Presenter:** Gregg Pollack
+
+## Abstract
+
+> So you’ve got the basics of Rails down, but you haven’t really done any testing. Never fear, this course will lead you through everything you need to know to start testing your Rails apps. All you need to bring is a laptop with Wi-Fi and a browser which isn’t Internet Explorer. All coding will be done through our web application, and there will be plenty of lab assistants to help you if you get stuck along the way.
+>
+> Topics Covered
+> * Test Unit basics
+> * Testing Rails models, using fixtures, and validation testing.
+> * Improving our testing code with macros, shoulda basics, and setup/teardown.
+> * Mocking and Stubbing with Mocha
+> * Testing the whole Rails stack with Capybara Integration tests
+> * Using Factory Girl to replace Fixtures
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
23 Rails-for-Zombies-(AKA-Intro-to-Rails-Part-1).md
@@ -0,0 +1,23 @@
+**Presenter:** Gregg Pollack
+
+## Abstract
+
+> Do you need to start learning Ruby on Rails? In this morning tutorial the Envy Labs team will lead you through all five labs of their Rails for Zombies course. Unlike other tutorials, all you need to start coding Rails is a laptop with Wi-Fi and a browser which isn’t Internet Explorer. All coding will be done through our web application, and there will be plenty of lab assistants to help you if you get stuck along the way. Before you come to the course we recommend you play through http://www.tryruby.org/. It’s an in-browser Ruby tutorial.
+>
+> Topics Covered
+> * Basic ActiveRecord CRUD
+> * Models, Validations, has_many, belongs_to
+> * Views, ERB, Loops
+> * Controllers, before filter
+> * Basic Routing
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
23 Rails-for-Zombies-2-(AKA-Intro-to-Rails-Part-2).md
@@ -0,0 +1,23 @@
+**Presenter:** Gregg Pollack
+
+## Abstract
+
+> Done with Rails for Zombies but can't stop the craving for a second corpse? We’ll pickup where Rails for Zombies 1 leaves off and jump into the topics listed below. All you need to bring is a laptop with Wi-Fi and a browser which isn’t Internet Explorer. All coding will be done through our web application, and there will be plenty of lab assistants to help you if you get stuck along the way.
+>
+> Topics Covered
+> * How to create a Rails app, the command line, database migrations, the Ruby 1.9 Hash Syntax, Bundler, and Database configuration.
+> * Named Scope, Callbacks, Include, has_many, and has_many :through relationships.
+> * REST principles, view forms, nested resources, and view partials.
+> * Sending email from our Rails app and the Rails 3.1: the Asset Pipeline.
+> * Controller rendering options and custom RESTful routes. Design an API with Rails and respond to AJAX requests.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
30 Rails:-The-Next-Five-Years.md
@@ -0,0 +1,30 @@
+**Presenter:** Yehuda Katz
+
+## Bio
+
+> Yehuda Katz is a member of the Ember.js, Ruby on Rails and jQuery Core Teams; he spends his daytime hours at the startup he founded, Tilde Inc.. Yehuda is the co-author of the best-selling jQuery in Action, Rails 3 in Action, and is a contributor to Ruby in Practice. He spends most of his time hacking on open source--his main projects, along with others, like Thor, Handlebars and Janus--or traveling the world doing evangelism work. He blogs at http://yehudakatz.com and can be found on Twitter as @wycats.
+
+## Abstract
+
+> When Ruby on Rails burst onto the scene in 2004, it excited web developers by showing that you could build next generation apps quickly and efficiently. Rails was one of the first frameworks to embrace Ajax, giving everyone the power to do partial page updates and whiz-bang effects in a conventional, effortless way.
+>
+> In 2007, the Rails team embraced RESTful conventions, making API development a no-brainer for new applications. Because RESTful JSON is so easy in Rails, Rails applications tend to implement APIs on balance.
+>
+> Then it was time to polish. Both the 2.0 and 3.0 releases cleaned up the code-base and found ways to take emerging conventions and make them easier to use.
+>
+> But now, like in 2004, another revolution is brewing. Increasingly, developers are moving their view layer from the server into the client, using RESTful JSON and client-side templating to increase responsiveness and bring applicable aspects of desktop applications to the web.
+>
+> Like last time, not every application needs to jump head-first into this new world. But just as in 2004, Rails has an opportunity to embrace the future, and bring its ruthless insistence on convention over configuration to bear on this problem.
+>
+> Rails already has the plumbing to be a fantastic conventional JSON server. The question is: will we take the challenge, or will we desperately cling to the past, hoping that the future will never come?
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 Railsflavored-Ruby.md
@@ -0,0 +1,16 @@
+**Presenter:** Michael Hartl
+
+## Abstract
+
+> Based on Chapter 4 of the Ruby on Rails Tutorial by Michael Hartl, “Rails-flavored Ruby” covers the aspects of the Ruby programming language most important for developing Rails applications. Topics include hashes, arrays, and other objects; blocks; functions; and classes.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
32 Realtime-web-applications-with-streaming-REST.md
@@ -0,0 +1,32 @@
+**Presenter:** Brad Gessler
+
+## Bio
+
+> I'm the CTO at Poll Everywhere, the worlds largest mobile survey platform, and I love building stuff. I've been hacking Rails since 1.x, full embraced REST, and haves since extended the concept to make building realtime Rails application easier.
+
+## Abstract
+
+> As more people collaborate on the web with your applications, its not enough to just persist data to the database; it needs to be pushed out to your users web browsers so that they're always working with the freshest data.
+>
+> In this session, Brad will show how to build a real-time layer on top of an existing Rails application's authorization and resource logic so that you can build on top of the hard work already invested in your Rails application.
+>
+> Topics that will be discussed include:
+>
+> - Why I didn't choose Socket.IO
+> - Stream application resources into Backbone.js models to keep data fresh
+> - Hook into ActiveRecord to push representations of data into a message queue
+> - Message queue naming conventions public/private resource streams
+> - Exposing message queues to HTTP
+> - Securing streams with existing application authorization logic
+> - Considerations for streaming in a production environment
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
31 Redis-Application-Patterns-in-Rails.md
@@ -0,0 +1,31 @@
+**Presenter:** Obie Fernandez
+
+## Bio
+
+> Obie Fernandez is an author and entrepreneur. He founded Hashrocket in 2007 and led it to prominence as one of the world’s leading Rails-based design and development shops. He is also a frequent speaker at industry events and is Addison Wesley’s Series Editor for the bestselling Professional Ruby Series. Prior to Hashrocket, as a senior consultant at ThoughtWorks, Obie specialized in complex custom enterprise software projects. His latest startup is DueProps.com, a promising new web startup that aims to revolutionize the way that people are recognized at work.
+
+## Abstract
+
+> Redis is a darling of the NoSQL crowd and for good reasons. It's easy to setup and has blazing fast performance. In this talk, drawn on real production experience and real code straight out of the DueProps codebase, Obie will introduce and demonstrate key Redis application patterns vital to today's Rails developer. Emphasis will be placed on real-world constraints and how to leverage Redis to improve scaling and performance over plain-vanilla ActiveRecord applications.
+>
+> Concepts covered:
+> * Adding Redis-based flags and other properties to ActiveRecord objects
+> * Event tracking with Redis sets
+> * Graphing relationships between (User) objects with Redis sets
+> * Time-ordered activity feeds with Redis sorted sets
+> * Applying security restrictions to display of activity feeds with intersection of Redis sorted sets
+> * Aggregating group activity feeds with union of Redis sorted sets
+> * Applying Redis sorted sets to scoring and leaderboard programming
+> * Integrating Redis with Rspec and Cucumber
+> * Debugging tactics for when things go wrong or are unclear
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 Rich-Hickey-Keynote.md
@@ -0,0 +1,16 @@
+**Presenter:** Rich Hickey
+
+## Abstract
+
+> Rich Hickey, the author of <a href="http://clojure.org/">Clojure</a> and designer of <a href="http://datomic.com/">Datomic</a>, is a software developer with over 20 years of experience in various domains. Rich has worked on scheduling systems, broadcast automation, audio analysis and fingerprinting, database design, yield management, exit poll systems, and machine listening, in a variety of languages.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
31 RoRoRoomba-Ruby-on-Rails-on-Roomba.md
@@ -0,0 +1,31 @@
+**Presenter:** Charles Abbot
+
+## Bio
+
+> Charles works at COOKPAD, Japan's largest recipe site and Rails shop. He spends most of his daylight hours building reporting, analytic, and payment management systems that millions of loyal users don't actually get to see. When he's not at work graphing bell-curves, forecasting user behavior, and throwing around gut-wrenching terms like "correlation-coefficients" and "confidence intervals" - he likes to play basketball, prepare his Roomba for the robot uprising, and dote on his newborn daughter. Charles has been using Ruby and Rails since Feb of '06.
+
+## Abstract
+
+> RoR makes an excellent framework for off-the-beaten-path type of projects, like hacking Roombas and other robots. In this presentation, I'll demonstrate how our soon to be robot overlords will be happy when we gift them with RoR and a connection to the internet. The presentation will include working examples and demonstrations of:
+>
+> - communicating with an Arduino chip via Ruby
+> - tethered serial and wireless bluetooth control of a Roomba via Ruby and Arduino
+> - two-way communication with our robot friends over the web using Ruby on Rails and popular web services
+> - useful applications of robots controlled over the web
+> - 3 RoRoR pitfalls to watch-out for
+> - live performance of "Chiron Beta Prime" by Jonathan Coulton*
+>
+> The presentation will close with an argument for why hacking on fun, often eccentric, projects in your spare time is essential for staying motivated, habitual improvement, and tangential learning -- i.e., being a real pragmatic programmer.
+>
+> *not included, perhaps
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
20 Ruby-Hero-Awards-Keynote.md
@@ -0,0 +1,20 @@
+**Presenter:** Ruby Hero Awards
+
+## Abstract
+
+> There are many people in the Ruby/Rails world who contribute to our community and rarely receive any recognition or payment for their work.
+>
+> They create educational content, develop plugins & gems, contribute to open source projects, and even put on events which help educate and make our lives as developers easier.
+>
+> Ruby Heroes was created to show some gratitude and give these people the recognition they deserve. Hopefully the type of recognition that keeps them doing what they’re doing, and continuing to make our community stronger.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
33 Ruby-Rogues-Live-Keynote.md
@@ -0,0 +1,33 @@
+**Presenter:** Ruby Rogues Live
+
+## Abstract
+
+> Ruby's favorite podcast comes to RailsConf! Join the Ruby Rogues (David Brady, James Edward Gray II, Avdi Grimm, Josh Susser, and Charles Max Wood) for this live episode on What Rails Developers Should Care About.
+>
+> If you've listened to the show, you probably know that the Rogues favor:
+>
+> * Good Object Oriented design
+> * Patterns
+> * Test Driven Development
+> * The Law of Demeter and Tell, Don't Ask
+> * Open source
+> * Beautiful code
+> * Pair programming
+> * Code metrics
+> * Scaling performant code
+> * and more
+>
+> Since this is a live episode, we want to interact with the audience. Each Rogue will give a brief introduction on what's important to him as a Rubyist on Rails, then we will turn the session over to your questions. We will take them over the Internet and/or live, before and during the show.
+>
+> All that AND we promise to wear amazing hats!
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
30 Sand-Piles-and-Software.md
@@ -0,0 +1,30 @@
+**Presenter:** Zach Dennis
+
+## Bio
+
+> Zach Dennis is a Software Craftsman/Partner at Mutually Human Software in Grand Rapids, MI. He's a proven RSpec and Ruby guru, founder of the Michigan Ruby User Group and co-author of The RSpec Book. He's contributed to several projects such as Ruby's standard library documentation, Ruby on Rails, and RSpec as well as many of his own. He's been leading and mentoring teams for almost an entire decade. In his spare time he reads copiously and plays the guitar. You can find him as @zachdennis on Twitter and @zdennis on Github.
+
+## Abstract
+
+> This talk applies the concepts of chaos theory to software development using the Bak–Tang–Wiesenfeld sand pile model as the vehicle for exploration. The sand pile model, which is used to show how a complex system is attracted to living on the edge of chaos, will be used as a both a powerful metaphor and analogy for building software. Software, it turns out, has its own natural attraction to living in its own edge of chaos. In this talk, we'll explore what this means and entertain questions for what to do about it.
+>
+> The speaker's hypothesis is that by understanding how complex systems work we can gain insights to better understand and improve the act of building software. By looking through the lens of the sand pile model we'll explore the following:
+>
+> * what the sand pile model can tell us about software development
+> * how software is naturally attracted to its own chaos
+> * the impacts on software living perpetually on the edge of chaos
+> * how existing software practices can be used to detract software away from chaos
+> * what this means not only for our software, but for our teams, and ourselves individually
+>
+> This thought-provoking perspective will leave you with new ways to think about software. You’ll walk away having learned a little about chaos, complexity, and how they apply to software with a thought-provoking perspective and inspiration for thinking about software in new ways.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
26 Schemaless-SQL-The-Best-of-Both-Worlds.md
@@ -0,0 +1,26 @@
+**Presenter:** Will Leinweber
+
+## Bio
+
+> As a member of Heroku's incomparable Department of Data, Will runs the world's largest Postgres service. He enjoys improving experiences, pushing boundaries, and simplifying everything. @leinweber
+
+## Abstract
+
+> Schemaless database are a joy to use because they make it easy to iterate on your app, especially early on. And to be honest, the relational model isn't always the best fit for real-world evolving and messy data.
+>
+> On the other hand, relational databases are proven, robust, and powerful. Also, over time as your data model stabilizes, the lack of well-defined schemas becomes painful.
+>
+> How are we supposed to pick one or the other? Simple: pick both. Fortunately recent advances in Postgres allow for a hybrid approach that we've been using at Heroku. The hstore datatype gives you key/value in a single column, and PLV8 enables JavaScript and JSON in Postgres. These and others in turn make Postgres the best document database in the world.
+>
+> We will explore the power of hstore and PLV8, explain how to use them in your project today, and examine their role in the future of data.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 Securing-the-Rails.md
@@ -0,0 +1,16 @@
+**Presenter:** Aaron Bedra
+
+## Abstract
+
+> Building safe web applications isn’t always easy. The good news is that Rails provides a lot of features that will help you along the way. Aaron will walk you through the common mistakes made by web developers, and how to account for them while working with Rails. He will also walk you through some tools you can use to make securing your applications much much easier.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
26 Securing-your-site.md
@@ -0,0 +1,26 @@
+**Presenter:** Thomas Pomfret
+
+## Bio
+
+> Thomas is CTO at Mint Digital where he has worked since the very beginning after acing the interview almost purely on the back of a sharp suit. Having been involved in all of Mint's major projects he has great real world experience in developing mass participation web sites quickly and effectively along with some hard lessons learnt on how to make them stay up. He mainly hacks in ruby although has a growing love for erlang.
+>
+> Past speaking gigs include Scotland on Rails, London Ruby Users Group and Kings of Code.
+
+## Abstract
+
+> Rails makes it very easy to rapidly develop web applications, but doesn’t always make it so simple to deploy or secure them.
+>
+> This talk is going to focus on best practices to secure your rails application, learnt through multiple high profile projects and penetration tests. The talk will be practical and show that this isn’t necessarily hard if thought about from the start.
+>
+> We’ll also touch on getting the right balance of security without it getting in the way of the users.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
22 Semi-Automatic-Code-Review.md
@@ -0,0 +1,22 @@
+**Presenter:** Richard Huang
+
+## Bio
+
+> Richard Huang is a senior engineer, a passionate rubyist and open source advocate, he created <a href="https://github.com/railsbp/rails_best_practices">rails_best_practices</a> gem, and also built the websites <a href="http://rails-bestpractices.com">rails-bestpractices.com</a> and <a href="http://railsbp.com">railsbp.com</a>
+
+## Abstract
+
+> Rails is so popular to be used to fast build a website, at the beginning we sometimes write codes too fast without considering code quality, but after your company grows fast, you have to pay more attentions on code review to make your website more robust and more maintainable.
+>
+> In this talk I will introduce you a way to build a semi automatic code review process, in this process a tool will analyze the source codes of your rails project, then give you some suggestions to refactor your codes according to rails best practices. It can also check your codes according to your team's rails code guideline. So engineers can focus on implementation performance, scalability, etc. when they do code review.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
34 Stack-Smashing.md
@@ -0,0 +1,34 @@
+**Presenter:** David Czarnecki
+
+## Bio
+
+> David Czarnecki is a lead engineer at Agora Games (a part of Major League Gaming), http://www.agoragames.com, a company that specializes in building middleware to power video games, both in-game and on the web. He is the author of 2 books for O'Reilly and had previously been developing exclusively in Java for nearly 15 years. He has been developing in Ruby and Rails since joining Agora Games in 2008 and has been a speaker at conferences like JavaOne, RailsConf and Ruby Midwest. David loves video games, especially the Guitar Hero series and Left 4 Dead.
+
+## Abstract
+
+> "Stack Smashing" refers to an internal project where I took our production Rails application environment down from over 100 virtual machines to 2 physical machines. Our application environment for Major League Gaming consists of 13+ inter-connected applications with millions of users to provide functionality such as single-sign on, online video (both video on demand and UGC), news and live competition information, photo galleries, profiles, and much more. We simply needed a simpler infrastructure in which to develop and deploy our applications. In this talk, we will cover the following:
+>
+> * Network topology before and after, as well as the makeup of our virtual and physical machines.
+> * Detailed discussion of Chef recipes, NGINX, HAProxy configurations and updates to standard configurations.
+> * Application and service monitoring and configuration.
+> * Application migration from the old stack to the new stack.
+> * Rails 3 to Rails 3.1 upgrade insights.
+> * Unicorns!
+> * Strategies for service configuration to handle failure.
+> * Offline processing with queueing and queue management.
+> * Simplifying, standardizing and sexy-fying your Capistrano-based deployment tasks into a reusable gem.
+> * Behavior driven infrastructure monitoring and validation.
+> * Adopting an opt-in continuous deployment strategy that is integrated with our continuous integration environment.
+>
+> This will be a very code and example-focused talk. Come and learn about the ways that you can simplify your existing infrastructure.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
20 Sustainable-Productivity-with-Rails.md
@@ -0,0 +1,20 @@
+**Presenter:** Xavier Shay
+
+## Bio
+
+> Xavier Shay recently emigrated from Australia to San Francisco to work on the engineering team at Square. Prior, he worked on large Ruby on Rails projects at The Conversation, NZX, Redbubble, and mentored many more. In 2010 he presented a world tour of a training course titled "Your Database Is Your Friend". He has been working with Ruby on Rails for half a decade, and has published and contributed to over 80 open source projects according to GitHub.
+
+## Abstract
+
+> Ruby on Rails claims to be "optimized for programmer happiness and sustainable productivity." I strongly disagree with the latter assertion. In this talk I will channel my half decade of industry Rails experience into expounding this position and providing constructive feedback as to what needs to change---in both the framework and the community---before we can support this claim. I'll also cover practical techniques you can use to be sustainably productive on your own projects in the meantime.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
45 Taming-the-Kraken-How-Operations-enables-developer-productivity.md
@@ -0,0 +1,45 @@
+**Presenter:** Nathen Harvey
+
+## Bio
+
+> Nathen Harvey is the manager of Web Operations for CustomInk.com, a website that allows you to design and purchase custom apparel for your group or special event. Nathen is the co-organizer of the Washington DC MongoDB Users' Group and DevOps DC. Nathen contributes to open source projects including the Opscode Chef framework. When not working or hosting meetups, Nathen enjoys going to concerts, drinking craft beer, and over sharing on sites like twitter, untappd, and foursquare.
+
+## Abstract
+
+> Are you having trouble launching new features because of friction between development and operations? At CustomInk, we've reduced this friction by making changes to our teams, processes, and tools. Come find out what we've been up to and learn how you can implement similar changes in your own environment.
+>
+> There's always a bit of tension when getting features from idea to production. In this talk, we'll look at some of the changes CustomInk has made to reduce this friction and keep the new features coming. Gone are the days of bi-monthly deploys, office pools dedicated to guessing when this deploy will be rolled back, and the ceremony surrounding the deploy-rollback-fix-deploy cycle. Today, ideas flow from product managers to developers to production with ease thanks to a number of changes that we've made to our teams, processes and tools.
+>
+> During this talk, we'll look at:
+>
+> * How product managers drive the release cycle
+> * Ideas and customer feedback
+> * Prioritizing development requests
+> * Managing branch merges and deployments (yes, product managers can help here!)
+>
+> * How operations enables developer productivity
+> * Spinning up development environments - Vagrant, Chef
+> * Infrastructure Automation - Chef
+> * Enabling Continuous Deployment - Capistrano and caphub
+> * Failing gracefully - Fault-tolerant load balancing with ldirectord
+>
+> * How developers get their code running in production
+> * Staging environments
+> * Continuous Integration - Jenkins, Green Screen
+> * Staying on topic: Deploying changes when they're ready
+>
+> * Getting rid of the over-the-wall mentality - Dev & Ops working together
+> * Enabling developers to do it themselves
+> * Pair programing infrastructure automation
+> * Keeping the process light and the communication flowing
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
24 Ten-Things-You-Didn't-Know-Rails-Could-Do.md
@@ -0,0 +1,24 @@
+**Presenter:** James Edward Gray II
+
+## Bio
+
+> James (@JEG2) has been a Rails programmer for about as long as it has been fashionable to be one and a Rubyist even longer than that. As you probably know from listening to him on the Ruby Rogues podcast, James loves to dig into how our community and code works.
+
+## Abstract
+
+> Rails is huge. Even if you have worked with it for a long time, it's unlikely that you have stumbled across everything yet.
+>
+> Do you really know what all of the built-in Rake tasks do? Have you seen all of the methods ActiveSupport makes available to you? Are you aware of all the queries ActiveRecord is capable of?
+>
+> In this talk, I'll dig into the extras of Rails and see if I can't turn up some features that you don't see all of the time, but that might just be handy to know about anyway. I'll make sure you come out of this able to impress your friends at the hackfest.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 Testing-Best-Practices,-or-The-Five-Habits-of-Highly-Effective-Tests.md
@@ -0,0 +1,16 @@
+**Presenter:** Noel Rappin
+
+## Abstract
+
+> There’s all kinds of discussion on how to make test processes work, and how to make tests fast, but it sometimes seems like there’s not much discussion on how to make tests useful. What makes a BDD test valuable, in that it will save more time that it will cost in maintenance? I’ll claim that there are five things that you should look for in your tests: independence, repeatability, clarity, conciseness, and robustness. These features will make the tests easier to write, easier to verify, and easier to keep consistent as your application becomes more complicated. You’ll leave this talk ready and able to write great tests.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
21 The-Future-of-Sass.md
@@ -0,0 +1,21 @@
+**Presenter:** Hampton Catlin
+
+## Bio
+
+> Hampton Catlin is the inventor of Sass, a CSS generating language, and the Haml markup language.
+> He is currently the Director of Engineering at Moovweb, a (bootstrapped!) startup focusing on transforming how we interact with the web. He is the original creator of Wikipedia Mobile (m.wikipedia.org) and is also the creator of several successful iPhone applications that have been downloaded by over 3 million people.
+
+## Abstract
+
+> A glimpse of some of the features coming to Sass in the pending 3.2 release. Plus, a huge announcement about the project that's been months in the making as we have secretly toiled away on something that we think will be awesome. Hear it first at this talk. Repositories will be made public when the talk is over. Shh! Its a secret!
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
22 Use-the-Source,-Luke:-High-fidelity-data-with-event-sourcing.md
@@ -0,0 +1,22 @@
+**Presenter:** Keith Gaddis
+
+## Bio
+
+> Keith Gaddis is a developer with almost fifteen years experience developing complex web applications, in industries ranging from medical applications to publishing to sports media. He has over six years experience with Ruby and Rails, and has been building complex web applications for more than a decade.
+
+## Abstract
+
+> Ever run into a really gnarly data problem and wished you had a do-over? Tired of wrestling with ActiveRecord to model a really complex domain? Looking for a good way to echo state changes to external systems? Then grab a cup of joe and settle in for a look at event-sourcing your data.
+>
+> Event-sourced data uses Plain Old Ruby Objects (POROs) to model your data and exclusively uses events to mutate state on those objects. By serializing the events, the state of your data can be recreated for any point in time, and outside listeners can create specialized purposeful datastores of the data, enabling complex business requirements with fewer hassles. We'll also touch on other architectural patterns like DCI and CQRS that play well with this idea.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
22 Using-Backbone.js-with-Rails:-Patterns-from-the-Wild.md
@@ -0,0 +1,22 @@
+**Presenter:** Sarah Mei
+
+## Bio
+
+> Sarah Mei is a Ruby and JavaScript developer from San Francisco. She has been programming since the days when Java was the new hotness, and for the last two years she's been at Pivotal Labs. She's on the core team for Diaspora and Pie, and contributes code to many other open source projects. She also co-founded RailsBridge, a non-profit that has taught more than 600 people how to program in the last three years.
+
+## Abstract
+
+> Backbone.js is a flexible, lightweight tool for structuring the JavaScript in a modern web application. It goes great with Rails! But beware - "flexible and lightweight" are code words for "you build your own plumbing." Backbone is new enough that we haven't established strong patterns for that plumbing yet, so different Backbone codebases look very different, and when you're new to the idea of structuring your JavaScript, it can be tough to tell where the win is.
+>
+> So in this talk I'll demystify Backbone. I'll show several very different ways I've used it on real Rails apps. You'll get a feel for the circumstances when Backbone makes sense, and moreover, when each of the different approaches to Backbone make sense.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
24 Using-Rails-without-Rails.md
@@ -0,0 +1,24 @@
+**Presenter:** Piotr Sarnacki
+
+## Bio
+
+> I'm passionate rails developer that loves open source. I was participating in Ruby Summer of Code 2010 with "Rails 3 Mountable Apps" project and I still try to contribute to Rails as much as I can.
+
+## Abstract
+
+> Rails got much more modular after 3.0 rewrite. But do you know how to use specific rails elements outside Rails? What if you would like to use ActionView with some other library (like webmachine)? Have you ever needed to render view with layouts outside of the rails stack? Or maybe you wanted to build some kind of system that fetches templates from database rather than from files? Router anyone? You know that you can use it outside rails too?
+>
+> In this talk I will dive into Rails internals and will show you what's there and how you can use it outside rails.
+>
+> Although I will focus on using those parts standalone, this knowledge will most likely help you also build your apps if you ever need something sophisticated that requires modification of regular rails behavior.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
16 Welcome-Keynote.md
@@ -0,0 +1,16 @@
+**Presenter:** Welcome
+
+## Abstract
+
+> Welcome to RailsConf 2012!
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
34 What-a-long-Strange-Trip-it-has-been..md
@@ -0,0 +1,34 @@
+**Presenter:** Ezra Zygmuntowicz
+
+## Bio
+
+> Ezra Zygmuntowicz is one of the early pioneers in the rails space. He was one of three original founders of Engine Yard and spearheaded much of the open source culture and community support for ruby in general that the company was built on. He is the author of Deploying Rails Applications for there pragmatic programmers and released one of the earliest commercial websites written in Rails back in fall of 2004 for the Yakima Herald Republic Newspaper.
+>
+> Ezra is the "deployment guy", when you look back in history on the rails mailing list you will find literally thousands of posts about deployment and helping the community figure out how to deploy and scale rails apps when no one knew how to do it.
+>
+> Ezra has build multiple clouds from the ground up. One IaaS cloud for Engine Yard before there was the term cloud at all, before EC2 existed even. He also built 2 PaaS clouds, Appcloud, Engine Yard's current AWS PaaS platform and Cloud Foundry a VMWare project. I think it may be safe to say that he has deployed more rails apps personally then anyone else on the planet.
+>
+> Ezra is a speaker at many ruby and cloud related technology conferences and has spoken at every single railsconf since the first one but missed out on speaking at the last 2 events.
+>
+> Ezra has become a Extroverted Mad Scientist Recluse with entrepreneurial tendencies and more recently has gone back to his roots in the physical world building many embedded electronics projects, blowing glass artwork, building and using multiple 3d printers, CNC machines and Laser cutters and recently even built his own CO2 laser from scratch!.
+>
+> He has come full circle from artists to technologist and back again, this time applying the technology of rails, ruby,cloud and the internet to classic artwork in mediums like Glass, QWood, Metals and Plastics. He is now slowly building the Internet of Things.
+
+## Abstract
+
+> This talk will explore the story of Ezra's travels through the history of ancient Rails 0.6 when he first picked it up in 2004 all the way through current times and extrapolate out to the future of the Rails and Ruby platform and how much of a success it has been. We will talk about the twisting path from way back then to now and beyond and explore what Rails was, is and will be as time keeps on slipping into the future.
+>
+> This talk will be chock full of aqdvancxed tech as well as ramblings of a Rails industry Vet who has been "On the Rails" for *8* long years now and has played a major part in shaping what has been, is and will be(at least in his own mind where he is absolutely a legend, in reality he's just a schmuck who hacks ruby)
+>
+> I want to share with the Rails community my story and experiences and hopefully impart some wisdom and some hard learned lessons about life, liberty and the pursuit of a rails app that doesn't use 400Mb of RAM per process ;)
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
24 Zero-downtime-deploys-for-Rails-apps.md
@@ -0,0 +1,24 @@
+**Presenter:** Pedro Belo
+
+## Bio
+
+> Hailing from Brazil, Pedro moved to the US and A and joined Heroku back in 2008, taking projects ranging from Node.js support to organizing Starcraft nights. Today he works on the API team, focused on making the Heroku public APIs smoother.
+
+## Abstract
+
+> What does it take to deploy an application without any downtime?
+>
+> More than most Ruby developers would expect, turns out; what is aggravated by the lack of documentation and other resources on this topic.
+>
+> In this talk we'll dive into both development practices (hot compatibility, database migrations, caching) and deployment setup (Heroku, Unicorn, HAProxy), covering everything you need to know in order to ship code without affecting a single customer.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)
View
20 i18n-on-Rails:-A-Twitter-Approach.md
@@ -0,0 +1,20 @@
+**Presenter:** Cameron Dutro
+
+## Bio
+
+> Cameron Dutro has worked for Twitter's International Team for about a year and a half, helping build and maintain the Translation Center, Twitter's crowdsourced translation platform. Although he only started using Ruby and Rails a few years ago, he's a big fan of their extendibility and elegance. Cameron is also the author of the twitter_cldr gem, an attempt to bring JDK-level internationalization capabilities to the Ruby community.
+
+## Abstract
+
+> Twitter's internationalization (i18n) and localization (l10n) model doesn't follow traditional methods. Instead of contracting out to professional translators, Twitter maintains an active community of over 500,000 volunteers who have helped successfully launch Twitter in 28 languages, including right-to-left languages like Hebrew and Arabic. Learn about some of the technical challenges we face, how to translate a Rails application at scale, and what to do when the i18n gem and po files aren't quite enough. We'll take a look at the tricky stuff too, like dates, times, lists, plurals, alphabetization, and capitalization using the twitter_cldr gem, and go over internationalization best practices. Finally, we'll explain how to maintain internationalization of your Javascript alongside your Rails code for an end-to-end solution.
+
+## Notes
+
+* This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
+* If you're interested in the generator code, see the "generator" directory.
+* This layout is just a suggestion.
+* Bullet points might work well. Paragraphs too. Up to you. :)
+
+## External Links
+
+* [Some related website](http://www.example.com/)

0 comments on commit 23533b0

Please sign in to comment.