Rafael, What you leave out is more important than what you include. These are items from your list that I'd scratch out:
Hooks respond_to rendering errors (?) And I know this won't be a popular thing to say, but I'd leave out testing, TDD, RSpec, etc until people understand a little about what they're doing. Rails is challenging enough. - Jeff --- Jeff Casimir Jumpstart Lab by Casimir Creative, LLC http://jumpstartlab.com @jumpstartlab on twitter On Wed, Mar 30, 2011 at 8:51 PM, <[email protected]> wrote: > Topic: What should a beginner rails programmer knows? (or what should I > teach at my Rails classes) > > Rafael MVC <[email protected]> Mar 30 11:59AM -0700 ^ > > After running a few RoR basic classes, and I've been struggling to > define the content of the course. > > Talking to Rob yesterday at the march mingle, he gave me a goal, which is: > "They should leave knowing enough to what to google for" -- which I > think is a great goal, but how much is enough? > > My current content coverage goal is: > > Basic Ruby: ( this is a fast crash course for people that already > knows how to program in another language) > numbers, string > puts and gets > if, else, while each loop > Array, Hash > basic oo concepts (methods, class, attributes) > irb > AR: > Associations > Validations > Hooks > AC + Dispatch: > routes > MVC > params > respond_to > AV: > form_for > rendering errors > basic helpers (link_to img_tag, date_select) > partials > Basic gems: > paperclip > devise (?) > any other suggestions? > > Deployment/scm: > git > heroku deployment > > Testing: > rspec (or unit?) > TDD basic concept > > Did I miss something? Did I cover something that shouldn't be covered? > > > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
