tag:blogger.com,1999:blog-17092334.post7909167259511606731..comments2022-07-24T23:17:34.408-07:00Comments on Hello, I'm blogging at you now...: I am a leet rails haxor...Roy Pardeehttp://www.blogger.com/profile/10996820877401028516noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-17092334.post-74133541271496820772008-10-21T08:32:00.000-07:002008-10-21T08:32:00.000-07:00Hey John,Tough to say. I guess my inclination wou...Hey John,<BR/><BR/>Tough to say. I guess my inclination would be to go with your option 2.<BR/><BR/>Rails is, as they say "opinionated", and you're probably better off just learning how to go along w/its opinions than learning the framework and learning the extra bits you need to override its conventions.<BR/><BR/>But don't take my word for it--I'm really no expert. Surf around & ask on the rails-talk google group if you don't get a good sense of your best path.<BR/><BR/>Cheers!Roy Pardeehttps://www.blogger.com/profile/10996820877401028516noreply@blogger.comtag:blogger.com,1999:blog-17092334.post-78171340079447136812008-10-21T05:48:00.000-07:002008-10-21T05:48:00.000-07:00Do you have any advice for someone just starting i...Do you have any advice for someone just starting in Rails that already has an established DB? <BR/><BR/>1) Do I need to create the migrations?<BR/>2) Should I start from scratch and then port all of my old data over?<BR/>3) Ignore migrations all together?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-17092334.post-28816739646053258652008-03-15T13:54:00.000-07:002008-03-15T13:54:00.000-07:00awesome!awesome!mondehttps://www.blogger.com/profile/07255800408763345744noreply@blogger.com