On 24 April 2010 14:34, Marnen Laibow-Koser <li...@ruby-forum.com> wrote: > Colin Law wrote: >> On 23 April 2010 22:54, Dani Dani <li...@ruby-forum.com> wrote: >>> Thank you all. >>> >>> Why not use scaffold in production ? >> >> I know some are not keen on scaffolding, but personally I found it >> useful when getting started as it allows one to get to something that >> provides basic functionality without needing to understand fully what >> is going on. > > But what's going on is easy enough to understand and fundamental.
I am not sure that it is necessarily easy to understand for the absolute beginner. I think maybe what I meant was that having the code automatically produced and in front of one can help in the initial understanding of how to do basic things such as create and update such that they become easy in retrospect. I don't think there is an absolute answer as to whether scaffolding is a 'good thing' or not. I believe that, for me, it was helpful, but for others maybe not. Colin > >> There are down sides however as it can lead one to be >> over dependent on it and _never_ understand fully what is going on. >> For example many beginners assume that there must always be a >> one-to-one correspondence between controllers and models, which is >> definitely not the case. > > Exactly! -- 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-t...@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.
