search for: jmckible

In typical Java/J2EE applications, domain model object do not have much logic, they are basically data holders. It seems to be considered a sin to put persistence logic in the domain model objects, instead it should be put a DAO (Data Access Object). I have always thought this seems funny, after all, what seems more natural/object-oreiented?: user.save() or userDao.save(user) In Ruby/Rails,

I''m trying to use it_should_behave_like, and something seems to be wonky with the syntax. When I add :shared=>true, the DSL complains that the next line is the fixture declaration: /vendor/plugins/rspec/lib/spec/dsl/behaviour_eval.rb:137:in `method_missing'': undefined method `fixtures'' for #<Spec::DSL::EvalModule:0x324a2cc> (NoMethodError) Here''s the

I''ve written a new Rails howto guide. It covers installation of a development environment, how to use Subversion and Capistrano effectively, and deploying to production using Textdrive. It''s basically a compilation of all the best guides I''ve found, plus a few new things I''ve come up with. I''d love to have you take a look and let me know what

This is not a technical question persay, but since rails is all about opinions, I figured it was worth asking: Now that CRUD is on people''s minds as a way to design webapps, I''m wondering if anyone has put thought into a naming convention for relationships. Some relationships have good terms, like User -> Subscription -> Magazine. I''ve found working with