# Suggestions for Rails Patterns

**URL:** <https://www.ruby-forum.com/t/suggestions-for-rails-patterns/132861>\
**Category:** Rails\
**Created:** [March 25, 2008, 12:43pm UTC](https://www.ruby-forum.com/t/suggestions-for-rails-patterns/132861 "2008-03-25T12:43:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![waddilove](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/b5ac83/32.png) [@waddilove](https://www.ruby-forum.com/u/waddilove)\
**Post date:** [March 25, 2008, 12:43pm UTC](https://www.ruby-forum.com/t/suggestions-for-rails-patterns/132861/1 "2008-03-25T12:43:52Z")

</div>

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](http://tinyurl.com/2mxcjo)

as comments in the blog, email me or use twitter ( [http://twitter/jweiss](http://twitter/jweiss)  
).

Thanks,  
Jonathan

–  
Jonathan W.  
[http://blog.innerewut.de](http://blog.innerewut.de)