I agree that high coupling is bad. I strongly disagree about renaming, though.
The theory that you can get good design up front depends on having both a stable problem and a stable solution. Most places don't have stable solutions, because creation of software is usually an exploration of the solution space. (If you don't need to explore the solution space, that often means you should just buy something off the shelf.) Quite a number don't have stable problems, either. Some people have innovative competitors; others are doing startup-ish things.
As Keynes said, "When the facts change, I change my mind. What do you do, sir?" I think that applies to design as well, method names included.
The theory that you can get good design up front depends on having both a stable problem and a stable solution. Most places don't have stable solutions, because creation of software is usually an exploration of the solution space. (If you don't need to explore the solution space, that often means you should just buy something off the shelf.) Quite a number don't have stable problems, either. Some people have innovative competitors; others are doing startup-ish things.
As Keynes said, "When the facts change, I change my mind. What do you do, sir?" I think that applies to design as well, method names included.