Canada on Rails: Engines: Team Development with Rails
- works at a media buying company, a service. Not building anything that will be sold. Dev for many clients simultaneously.
- see the same needs across the clients
- deals with the most boring problems over and over
- reuse code when it solves the same problem, not when it looks for.
- these applications are not beautiful and unique snowflakes (_this joke is even better than you think because he looks like brad pitt_)
- Generators vs. Engines. _He talked for a while about this which I learned on the Engines Intro
- Use svn:external to keep engines up to date.
- “it is fun to use ruby for evil”
- engines are plugins but a tiny more that they found useful.
- a way to share MVC slices between apps
Last night I ate at a Brazilian place with 30 or so Railers. They serve meat on a sword. So he added refs to MeatSword here and there in his slides, including MeatSword.com…. which is a pr0n site… hilarity ensues when someone mentions he visited the URL in a Q&A and everyone loads it in to see for themselves
- wants happy coexistence with Rails Core