Permalink
Browse files

`$ script/add-redirect-links`

  • Loading branch information...
1 parent 2a8d1e2 commit 9a9aee306ce39a3fc81004ed9681deb6951d7664 @benjaminoakes benjaminoakes committed Jun 22, 2012
Showing with 315 additions and 7,227 deletions.
  1. +4 −3 Aaron-Patterson-Keynote-JA.md
  2. +4 −194 Aaron-Patterson-Keynote.md
  3. +4 −14 ActiveRecord-Scopes-and-Arel.md
  4. +4 −15 ActiveSupport-and-ActiveModel.md
  5. +4 −103 Basecamp-Next:-Code-Spelunking.md
  6. +4 −14 Basic-Rake.md
  7. +4 −91 COOKPAD-Keynote.md
  8. +4 −61 ...-multiple-feature-prototypes-in-production-for-test-segments-of-their-15-million-engaged-users.md
  9. +4 −55 CoffeeScript-for-the-Rubyist.md
  10. +4 −22 Complex-Made-Simple:-Sleep-Better-with-TorqueBox.md
  11. +4 −161 David-Cohen-Keynote.md
  12. +4 −189 David-Heinemeier-Hansson-Keynote-ES.md
  13. +4 −31 David-Heinemeier-Hansson-Keynote-JA.md
  14. +4 −39 David-Heinemeier-Hansson-Keynote-PT.md
  15. +4 −6 David-Heinemeier-Hansson-Keynote-RU.md
  16. +4 −185 David-Heinemeier-Hansson-keynote.md
  17. +4 −22 Deconstructing-Travis.md
  18. +4 −265 Designing-Hypermedia-APIs.md
  19. +4 −128 Digging-Deep-with-ActiveSupport::Notifications.md
  20. +4 −59 Evented-Ruby-vs-Node.js.md
  21. +4 −52 Extending-Ruby-with-Ruby.md
  22. +4 −135 From-Rails-Rumble-to-50,000,000-results.md
  23. +4 −72 Getting-Down-To-Earth:-Geospatial-Analysis-With-Rails.md
  24. +4 −124 Home.md
  25. +4 −90 How-You-Can-Help.md
  26. +4 −14 How-to-Find-Valuable-Gems.md
  27. +4 −170 Ignite-RailsConf.md
  28. +4 −14 Introduction-to-RSpec.md
  29. +4 −111 Its-Not-in-Production-Unless-its-Monitored.md
  30. +4 −26 Keeping-Rails-Applications-on-Track-with-Brakeman.md
  31. +4 −15 KidsRuby.md
  32. +4 −57 Let's-make-the-web-faster-tips-from-trenches-@-Google.md
  33. +4 −367 Lightning-Talks.md
  34. +4 −19 MiniTest:-Refactoring-Test-Unit-and-RSpec-back-to-version-0.0.1.md
  35. +4 −25 Mobile-Rage-What-causes-it-how-to-fix-it.md
  36. +4 −26 Patella:-It's-Memoization-into-Memcached-calculated-in-the-background-with-Resque..md
  37. +4 −54 Powerful-Interfaces.md
  38. +4 −253 Practical-Machine-Learning-and-Rails.md
  39. +4 −15 Preparing-for-Rapid-Growth---Tips-for-Enabling-Your-Rails-App-and-Team-to-Grow-Quickly.md
  40. +4 −115 Presenters-and-Decorators:-A-Code-Tour.md
  41. +4 −77 Progressive-Enhancement-on-the-Mobile-Web.md
  42. +3 −59 README.md
  43. +4 −15 RVM-Essential-Rails-Development-Tools.md
  44. +4 −123 Rails-Engines-Patterns.md
  45. +4 −36 Rails-Testing-for-Zombies.md
  46. +4 −21 Rails-for-Zombies-(AKA-Intro-to-Rails-Part-1).md
  47. +4 −21 Rails-for-Zombies-2-(AKA-Intro-to-Rails-Part-2).md
  48. +4 −95 Rails:-The-Next-Five-Years.md
  49. +4 −74 RailsCore-panel.md
  50. +4 −7 Railsflavored-Ruby.md
  51. +4 −79 Realtime-web-applications-with-streaming-REST.md
  52. +4 −29 Redis-Application-Patterns-in-Rails.md
  53. +4 −398 Rich-Hickey-Keynote.md
  54. +4 −7 RoRoRoomba-Ruby-on-Rails-on-Roomba-JA.md
  55. +4 −81 RoRoRoomba-Ruby-on-Rails-on-Roomba.md
  56. +4 −52 Ruby-Hero-Awards-Keynote.md
  57. +4 −299 Ruby-Rogues-Live-Keynote.md
  58. +4 −147 Sand-Piles-and-Software.md
  59. +4 −28 Schemaless-SQL-The-Best-of-Both-Worlds.md
  60. +4 −29 Securing-the-Rails.md
  61. +4 −119 Securing-your-site.md
  62. +4 −56 Semi-Automatic-Code-Review.md
  63. +4 −13 Software.md
  64. +4 −188 Speakers-on-Twitter.md
  65. +4 −32 Stack-Smashing.md
  66. +4 −136 Sustainable-Productivity-with-Rails.md
  67. +4 −323 Taming-the-Kraken-How-Operations-enables-developer-productivity.md
  68. +4 −37 Template.md
  69. +4 −458 Ten-Things-You-Didn't-Know-Rails-Could-Do.md
  70. +4 −14 Testing-Best-Practices,-or-The-Five-Habits-of-Highly-Effective-Tests.md
  71. +4 −65 The-Future-of-Sass.md
  72. +4 −108 Use-the-Source,-Luke:-High-fidelity-data-with-event-sourcing.md
  73. +4 −38 Using-Backbone.js-with-Rails:-Patterns-from-the-Wild.md
  74. +4 −82 Using-Rails-without-Rails.md
  75. +4 −8 Using-XMPP-As-an-Asynchronous-Communication-Layer-Between-Ruby-and-JavaScript.md
  76. +4 −8 Welcome-Keynote.md
  77. +4 −29 What-a-long-Strange-Trip-it-has-been..md
  78. +4 −23 Zero-downtime-deploys-for-Rails-apps.md
  79. +0 −1 _Header.md
  80. +4 −401 i18n-on-Rails:-A-Twitter-Approach.md
@@ -1,5 +1,6 @@
-TODO Summary of content (or whatever you'd like to contribute). [[Example in Portuguese|David Heinemeier Hansson Keynote PT]]
+We've Moved!
+------------
-## 他の言語
+The RailsConf 2012 wiki is now [a general Ruby conference wiki](https://github.com/newhavenrb/conferences/wiki).
-* [[English|Aaron Patterson Keynote]]
+Please find this page in its new home: https://github.com/newhavenrb/conferences/wiki/Aaron-Patterson-Keynote-JA
View
@@ -1,196 +1,6 @@
-**Presenter:** Aaron Patterson
+We've Moved!
+------------
-## Abstract
+The RailsConf 2012 wiki is now [a general Ruby conference wiki](https://github.com/newhavenrb/conferences/wiki).
-> 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
-
-### From @benjaminoakes
-
-* He does OSS at ATT Interactive
-* Works at home; his annual review is online
- * Goes through VPN
- * Browser isn't supported
- * Uses IE on a VM; still not supported
- * Needs to be IE7
- * Uses a Mac server
- * SSH tunnel to his laptop for VPN
- * "Rube Goldberg Network Architecture"
-* Aaron Patterson's title is now "Corey Haines" :)
-
-This talk is about failure
-
-* Tokaido ("Lampshade" -- I think)
- * From Yehuda Katz (@wycats)
- * Binary distro of Ruby + gems for Rails
- * Good for students; don't have to worry about dependencies
- * Good for teachers too; he used to teach Ruby at U. Washington
- * Good for all developers
- * Time is important
- * Shared objects, `dlopen`, `otool`, etc... what are these things?
- * If you're building and you have a problem with one of these, you need to know how they work
- * Do you want to spend time on this?
- * Needs good ecosystem
- * Alternative: "RailsBridge" project
-
-* Failure to evolve
- * Concurrency is important
- * Not enough
- * Why do we have **ActionMailer**? Sending emails, obviously...
- * Done synchronously (blocking; bad if slow)
- * Could get exception
- * Best case: slow, worst case: errors
- * Need to do in a backround job, etc (producer/consumer pattern)
- * Why do we have ActionMailer without a **Queue**?
- * We do... but no one uses it (**ActiveQueue**)
- * `queue << Runnable.new`
- * `ActiveQueue` doesn't actually have an implementation ("0 lines")
- * Lots of other options, but different interfaces
- * Interface is more important than implementation (e.g., Redis, AMQP, etc)
- * We don't have a driving force for this common API
- * Make it easy to switch
- * "I'd like to see Rails 4 be the driving force"
-
-* Failure to lead (fear of features)
- * Less tolerance for techical debt
- * `tolerance = value / time`
- * Younger: bad at predicting maintenance time; more tolerance
- * New developers more likely to merge without thinking about maintenance cost
- * Cosmetic
- * Tagged logging
- * Output: `[foo] [bar] omg!`
- * Not thread safe, incompatibility
- * 2nd one (I missed; had to shift focus :( )
- * Course correcting
- * "Asset pipeline" idea worked differently for every project in < 3.1
- * Not perfect
- * We're doing more client side computation now (rather than server side). JavaScript, etc.
- * Asset Pipeline too big to fail
- * No "technical debt" bailout
- * We need to be prepared for this
-
-### From @danbernier
-
-@tenderlove settles his stage nerves with inspiration from Freddie
-Mercury.
-
-He works for AT&T remotely. When he does his annual review, since he
-works from home, he VPNs in: where he's told that Chrome, Safari, and
-IE9 are all unsupported - he needs IE7.
-
-#### Failure
-
-Our own, and @tenderlove's. Talk title: "I've made a huge mistake."
-
-##### Tokaido project
-
-A binary of ruby for OSX, ready for rails. This is promising
-especially for students & teachers. (You always spend the first lesson
-just installing.)
-
-But for all developers: how important is your time? Installing ruby &
-all your gems from source is really complicated & arcane. Yehuda is
-gonna have to work with C-extension writers, and work on their tool
-chain.
-
-##### Concurrency
-
-Why do we have ActionMailer? It always slows down a request, when you
-have to send an email. So let's do it out-of-band, asynchronously. So,
-why do we have ActionMailer, but no Queue? We do: ActiveQueue, but it
-has no docs or examples, and lots of configuration; it actually has 0
-lines of code.
-
-Lots of queueing choices: Resque, AMQP, QueueClassic, delayed job,
-sidekiq...but they all have different interfaces. Why don't they all
-have a consistent API? The interface is more important than the
-implementation: queues should have push, consumers should have run, so
-we can swap easily. Rails 4 can be the driving force for this: provide
-a sample implementation to match.
-
-##### Failure to Lead
-
-Features, and a Fear of Features
-
-It _seems_ like older devs are afraid of features, but really, they're
-more afraid of technical debt - they have a lower tolerance for it. As
-you age, your tolerance for it dwindles.
-
-The value of a feature is its current value + its potential value.
-
-The cost of a feature is its dev time + its maintenance cost
-
-Tolerance = value / time
-
-Younger devs don't predict the time, & the value, less accurately. If
-you don't pay the maintenance cost, you have a higher tolerance for
-it. Young devs are more likely to merge requests in.
-
-So let's categorize rails features:
-* cosmetics: dubious value, unknown debt
-* refacturings: high value, low (maybe negative) debt
-* course-corrections: high value, unknown debt
-
-A cosmetic feature: tagged logging, which wasn't thread safe, & was
-incompatible. Dubious value, unknown debt. Why do we need this?
-
-A refactoring feature: notifications. Gave us less code, more
-information, smaller stack sizes.
-
-A course correcting feature: asset pipeline. It got us closer to
-on-course, but not quite there. We've gone from centralized
-mainframe/terminal, to distributed PC, to centralized browser/server,
-and now back to distributed JS rich clients. Asset Pipeline is too big
-to fail, because that's the direction we need to go, but we have to
-pay down this technical debt. The computation location is changing,
-moving to the browser.
-
-
-### From @jamesgary
-
-* Failure to Remember
- * Toukaidou
- * Binary distribution of Ruby w/ gems to run rails, executable
- * Easy, quick installation for students, teachers
- * As developers, how important is your time?
- * Things can go wrong, and you'll have to spend time researching how to fix it
- * Ecosystem
- * Yehuda has a lot of work to make things work (like C extensions)
- * Volunteer for RailsBridge
-* Failure to Evolve
- * Concurrency - Aaron hasn't been treating it as important as he should
- * Sending email should use Producer/Consumer pattern
- * We have ActionMailer, but no Queue
- * We do have ActionQueue, but no one uses it because it has no docs, examples, and needs lots of config
- * Lots of queuing tools, but all have different interfaces
- * Interface is most important, implementation is secondary
- * We need to demand a consistent API, but who is the driving force?
-* Failure to Lead
- * Features
- * Fear of features
- * Older developers might have a lower tolerance for technical debt
- * Newer developers have higher tolerance for tech debt
- * Value = Current + Potential
- * Cost = Dev Time + Maintenance
- * Tolerance = Value / Time
- * If you don't pay maintenance time, your tolerance is higher
- * New devs are more likely to click the merge button
- * Types of features
- * Cosmetic: Dubious value and unknown debt (tagged logging, since it was not thread safe and inconpatible)
- * Refactoring: High value and low (sometimes negative) debt
- * Course Correcting: High value and unknown debt: Asset Pipeline
- * Asset Pipeline is 'too big to fail', but we have no bail out
- * We need to be prepared
-
-## Discussion
-
-* He's talking about fear of features/change like DHH was... Maybe they discussed this at length? What's the impetus of this? (Have a link?) @benjaminoakes
-
-## External Links
-
-* [Tokaido railsapp kickstarter project](http://www.kickstarter.com/projects/1397300529/railsapp/posts)
-
-## Other Languages
-
-* [[日本語|Aaron Patterson Keynote JA]]
+Please find this page in its new home: https://github.com/newhavenrb/conferences/wiki/Aaron-Patterson-Keynote
@@ -1,16 +1,6 @@
-**Presenter:** Jacob Swanner
+We've Moved!
+------------
-## Abstract
+The RailsConf 2012 wiki is now [a general Ruby conference wiki](https://github.com/newhavenrb/conferences/wiki).
-> 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
-
-* [Slides](http://speakerdeck.com/u/jswanner/p/activerecord-scopes-arel)
+Please find this page in its new home: https://github.com/newhavenrb/conferences/wiki/ActiveRecord-Scopes-and-Arel
@@ -1,17 +1,6 @@
-**Presenter:** Bryan Liles
+We've Moved!
+------------
-## 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
-
-* ActiveSupport gives us pluralization and more, makes ruby better
-* Use pry instead of IRB
-* include ActiveSupport::Benchmarks, Rails uses benchmark for asset times
-* include ActiveSupport::Callbacks
-
-## External Links
-
-* [Pry (github)](http://pry.github.com/)
+The RailsConf 2012 wiki is now [a general Ruby conference wiki](https://github.com/newhavenrb/conferences/wiki).
+Please find this page in its new home: https://github.com/newhavenrb/conferences/wiki/ActiveSupport-and-ActiveModel
@@ -1,105 +1,6 @@
-**Presenter:** Nick Quaranto
+We've Moved!
+------------
-## Bio
+The RailsConf 2012 wiki is now [a general Ruby conference wiki](https://github.com/newhavenrb/conferences/wiki).
-> 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
-
-### From @benjaminoakes
-
-* Who
- * In Buffalo, NY (was in Boston)
- * 37signals
-* New version Basecamp
- * Architecture
- * Rails -> databases: [Elastic Search, Redis, MySQL Memcached] services: [Depot, porfolio, Launchpad, Queenbee (where the honey is made; does billing)]
- * "Rainbows" (does polling, related to Unicorn)
- * Only thing you need locally is Rails and MySQL. They wrote (and use) Pow
- * launchpad + portfolio
- * Testing
- * test/unit, mocha, [capybara](http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Node/Matchers) ("makes `assert_select` obsolete"), qrush/m
- * ...
- * Development setup
- * "All apps need to have reset button"
- * They call it `script/setup`. (We call it `./configure`, like for a C project, etc.)
- * `module YourConcern; extend ActiveSupport::Concern` pattern (interesting?)
- * Include a bunch of concerns in a controller
- * Adding stuff directly feels gross
- * 50/50 CoffeeScript/Ruby
- * wysihtml5 for rich editors
- * JS
- * jQuery plugins
- * Patterns:
- * extend jQuery: `$.fn.highlight = -> # ...`
- * Stacker
- * Replaces page
- * Incercepts clicks on `<a>`
- * Does `$.ajax`
- * Handles errors
- * based on History.js
- * Hooks
- * `page:*`
- * JS console mastery
- * `console.count('foo')`
- * `warn`, `error`
- * `group`, `groupEnd` (clumping)
- * `profile`, `profileEnd` (profiling even with a name -- goes in "Profiles" tab, looks awesome)
- * `debugger`, `console.trace` (stack trace)
- * `chrome.csi()` how long since page load
- * API Building
- * repo for docs: 37signals/bcx-api
- * rails/jbuilder
- * "view data in the views"
- * vs. ugly `as_json` vs `to_json` dance
- * "public JSON"
- * rails/strong\_parameters: uses `FooController#document_params`
- * It's a controller not a model problem (vs `attr_accessiblei`
- * Status codes belong in controller
- * HTTP 204
- * Logging
- * A lot
- * `???::TaggedLogger` (new in Rails 3.2) FIXME replace ???
- * literals or lambdas
- * Can use Rack environment for sharing data through this
- * Stats
- * `statsd`
- * See `ActiveSupport::NOtifications.instrument`
-
-## Discussion
-
-* `./configure` vs `script/setup`. One is a convention outside Ruby projects, the other isn't. Preference? @benjaminoakes
-* `Rails.env` in js via `.coffee.erb`. Hard to do when asset compiling though, right? It's always in production. @benjaminoakes
-
-## External Links
-
-* [Slides](http://speakerdeck.com/u/qrush/p/basecamp-next-code-spelunking)
-* [Pow](http://pow.cx/) - Mac only :(
-* http://httpstatus.es/204
-* Github TODO make into links
- * qrush/m - Runs tests by line number
- * xing/wysihtml5 - Rich text editor
- * josh/rails-behaviors
- * balupton/History.js - Abstracts history API
- * 37signals/bcx-api - their API docs, Markdown
- * rails/jbuilder - Renders JSON response
- * rails/strong\_parameters - filters parameters ("avoids the GitHub mess")
- * 37signals/marginalia - released yesterday; adds info at end of query log messages
- * ???/statsd TODO replace ???
- * ???/resque-statds TODO replace ???
+Please find this page in its new home: https://github.com/newhavenrb/conferences/wiki/Basecamp-Next:-Code-Spelunking
View
@@ -1,16 +1,6 @@
-**Presenter:** Jim Weirich
+We've Moved!
+------------
-## Abstract
+The RailsConf 2012 wiki is now [a general Ruby conference wiki](https://github.com/newhavenrb/conferences/wiki).
-> 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
-
-* TODO [Slides](http://www.example.com/)
+Please find this page in its new home: https://github.com/newhavenrb/conferences/wiki/Basic-Rake
Oops, something went wrong.

0 comments on commit 9a9aee3

Please sign in to comment.