I can't help but think that giving generic coding advice by using a dynamically typed language is anathema to a book, because you see all these symbols in the source (customer, account, etc...) but you have no idea what methods they respond to and which ones are compatible with which other ones.

I hope that as a senior software engineer, you make your points using other languages than Ruby in your book.