It's a long story, but in rubyland it's almost always a bad idea to use "and" rather than &&. Same with "not" and "!".

Actually you could rewrite this a bit...

```ruby
if @question.answered && @question.answers.any?
```

...but I'm wondering if you should simply change the implementation of "question.answered" from a boolean setting to something like this instead:

```ruby
def answered?
  answers.any?
end
```

and just use @question.answered? in your logic.