I think there's no good rule of thumb to be had here; use whichever style makes the code clearer.
At times, this means I have to skip a one-liner because it's not as clear as expanding it out; at other times, it means using a one-liner because it's clearer than an expanded form. Sometimes it means using #length on a String or Array, sometimes it means using #size. They do the same thing (much to the annoyance of some folks), but the fact that both work means I can think about how my code reads.
See this blog post for more info: http://www.skorks.com/2010/04/ruby-access-control-are-privat...
This is the reason I highlighted it. I had heard both sides of the argument from peers and was a little conflicted myself. Russ is simply the highest authority I've encountered to have an opinion on it.
Actually, new rubists might not even know that you can leave it out. In php you are required to use `$this->' for instance members.
I don't have the book in front of me so I don't know what the context is, but this strikes me as something as barely worth highlighting, other than to show that you grok Ruby's method chain.
Some programmers would argue that using self.method_name helps clear up ambiguity to humans who read the code, even if it is equivalent to method_name