[saraid216]

What he hand-waves is that he's got something that looks like this:

  def signed_out?
    # Code
  end
  
  def signed_in?
    !signed_out?
  end

Which can easily start to become its own problem. On the other hand, with Ruby, it might be worthwhile to define something like Class#invert such that you have this:

  def signed_out?
    # Code
  end
  method_invert :signed_out?, :signed_in?

Dunno. I haven't ever found myself in a position where it mattered.