Thanks a lot guys, I really appreciate your responses. Tutorials can say good things about popular gems and some common practices in rails development, etc.
And I think one of the things that we should do is trying to not to make the mistakes that already exist in rails projects. In most of the rails projects that I've seen there's no good OO design and mixing responsibilities is a common thing. Fat models and slow unit-tests are bad ideas which can be easily found in rails projects. We should strive for better separation of concerns and SOLID design in our application. These things can make good differences in the apps we write. Best Regards -- Sam Serpoosh Software Developer: http://masihjesus.wordpress.com Twitter @masihjesus -- 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@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en-US.
