>> Instead, look at it like this: how likely is a Giraffe able to do what
>> an Order does? If the Giraffe doesn't quack like an Order, than an
>> exception is going to be thrown automatically anyway.
>>
>> Just program in it, and see how often it ever actually bites you. Start
>> with small things, work your way up.
> 
> Good advice.

This kind of mindset is just asking for things to go wrong..

Lets say that the Giraffe happens to have a few methods that does match 
those of an order, so that it manages to introduce incorrect values that 
populate through your data before the exception is eventually caught.

(ofcourse a Giraffe is an extreme case, but multiple domain objects can 
have attributes that overlap, such as price, name etc)

And once you catch the exception, you have absolutely no clue at all 
what have been affected.

Incorrectness should be caught early before it litters your data, or you 
will have a seriously hard time debugging.

Just because the language is non strict when it comes to types doesnt 
mean you should not care about correctness?
-- 
Posted via http://www.ruby-forum.com/.