Friday, December 2, 2011
Thanks a lot Michael, if I can get sign-off what would be the right way to go about separating code. Try to leave the admin app alone and move the user facing and api app to rails 3.1 ? Would I then need to make a plugin for the models so I can share them between apps? Or should I use Engine?
Thanks,
-- On Fri, Dec 2, 2011 at 11:16 AM, Michael Pavling <pavling@gmail.com> wrote:
On 2 December 2011 14:08, Rog <rogsmith@gmail.com> wrote:That's not "refactoring" - that's writing new functionality.
> I have a question about refactoring, I just joined a company with a
> rails 2.3 code-base (pretty large and not many tests) this site has a
> user facing site, but the bulk of the functionality is for the admin
> facing portion of the site, I want to build a nice API with OAuth as
> ANy best practices here?
Good practice would be to get buy-in from your employers; explain to
them the reason for your desire to spend time on this development, and
explain about the benefits they'll gain. If they don't want you to do
it, then it's likely to be moot.
If you've not done so already, read the "Refactoring: Ruby Edition"
book, and start to try to apply its principles.
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment