Hello, Thanks for the reply. Definitely good to know :)
George On Tuesday, September 8, 2015 at 2:28:37 PM UTC+8, bot Peña wrote: > > On Tue, Sep 8, 2015 at 7:38 AM, George Mendoza <gsme...@gmail.com > <javascript:>> wrote: > > Our team lead and I recently discussed the pros and cons of breaking up > a > > long source file into multiple source files. I tend to prefer one class > per > > file, because I find the individual files easier to read and easier to > find > > (with ctrl-p in Sublime). > > on my case, my reason is simple. i edit a single responsibility. easy > for my brain and easy for my tests. > > > On the other hand, our team lead doesn't have > > issues with long source files. He argues that they are quite common in > > open-source projects. As an example, he pointed to the > > ActionDispatch::Routing::Mapper class in Rails as a case of a long file > with > > multiple inline classes. > > > i dont buy that argument (it has no argument really); the rails source > is not a god : ) > > choose what you think is easy for you, why you think it's easy, then > justify, demonstrate it to the group. > > kind regards > --botp > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/cebb1f72-0b37-4a26-b684-5445f07a5bf3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
