> This helpful Stack Overflow question should display why teaching noobs > scaffold first off is a bad thing: > http://stackoverflow.com/revisions/9622251/1. He's shown way too much code, > and if you take a look at his routes he has a whole bunch of actions that > probably don't need to be there. He has no idea what the controller provides > to the view or how that even works. > This guy has no idea what he's doing, I don't think that citing his case is at all useful. People can get confused no matter what you show them. > > We should teach them this *first* (create a controller, actions, etc.) and > then show them the shortcut to doing it (scaffold generator). Teaching them > scaffold first is wrong. It's a cheap trick that needs to die. > >
> I think that extracting it out into a gem and educating people on how Rails > should be taught would have the best impact. The people who still want to use > scaffolding for rapid prototyping can do that. > Once you know how the rest of it works, there's no purpose to having the scaffold generator. You're thinking about this thing completely backwards. After you know, using it is a cheap trick, before then it's a useful way to get an example and dig in. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
