On Thu, Aug 18, 2011 at 6:58 PM, Rodrigo Ruiz <rodrigo.ru...@gmail.com> wrote:
> Well, setting aside the code access concern, the other thing I wanted to > know is how to work in a team with rails, and I mean, how should I split my > project? Define the features you want to add to your project; give one to each developer, who will then write the tests and write the code. If you have a big enough or specialized enough team, you might have someone working specifically on refining views/CSS/graphics. Regardless, free and direct communication amongst the development team members is absolutely critical. Good luck! -- Hassan Schroeder ------------------------ hassan.schroe...@gmail.com http://about.me/hassanschroeder twitter: @hassan -- 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.