My first gut feeling was "kill it, kill it". But then, I am the kind of person that tends to spring-clean then regret throwing away too much.
The Wow factor is what got me into Rails in the first place, even though I quickly refactored the scaffold code I had generated ... and never looked back. Scaffolds help lower the barrier to newbies. I may not have jumped out of Java into Rails as quickly if that barrier was higher. But that was 2005 ... So I think it's an issue of education. Trainers, mentors and senior devs need to 'pace' newbies. 1) Show them scaffolds. Let them go 'wow.' 2) Develop an example to the point where scaffolds become problematic. Let them grok the cul-de-sac they're in. 3) Fix the problem by showing them how controllers are really developed. You can't go directly from step 1 to step 3, because many of them will still be basking in the glow of the wow. The won't be attending to what you're trying to show them. As some have said, their mental models could be distorted. Mark Ratjens -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/MxELMN9M7OYJ. 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.
