You can find more information on the speaker's site:
Code is often hard to understand!
Not because we don't understand the programming language, but because we are overwhelmed with details that effectively hide the original intentions of the developer.
As an example: we might ask someone to "turn on the light", we don't ask them to "go to the front of the room, look for a switch on the wall, and toggle it to its opposite state".
The same should be true of objects - and with some consideration, it's easy enough to do.
This talk follows this concept and suggests a couple of conventions for method naming and subroutine structure to help make your intentions easier to understand.