Agreed, and something to add in the explanation of what to do is the "why." When someone (or you) is reading the code later, you see a method call and know exa

Agreed, and something to add in the explanation of what to do is the "why." When someone (or you) is reading the code later, you see a method call and know exactly what it does. This prevents you from having to click in or find it just to figure out what it does. Frequently, if you click into a vaguely named method, it doesn't do the thing you were searching for and you wasted a little time and need to backtrack, only to repeat the cycle with other vaguely named methods.