Cheers,
Next week I''m going to present Rails Patterns at the Scotland on Rails
conference. The idea is to talk about common pitfalls and problems that
I''ve encountered in many of the Rails projects I''ve been
involved with
and describe a solution or best practice.
I''ve already assembled several scenarios like async media processing,
handling massive user data or deployment setups. I''m also curious what
kind of problems you have encountered in your Rails past so that I can
include them.
So if you have any suggestion to a common mistake that you see (like
throwing plugins at random problems just because it seems easier) or a
useful pattern that you use (like following "vendor everything" or how
you handle background jobs), please send them too me. You can post them here
http://tinyurl.com/2mxcjo
as comments in the blog, email me or use twitter ( http://twitter/jweiss ).
Thanks,
Jonathan
--
Jonathan Weiss
http://blog.innerewut.de
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
