Having already problems to find skilled personnel, a manager will think twice to pay more!

Especially if his competitors can solve more problems with less and cheaper hackers, just because they are guided by a strict framework / IDE.

Then he will rather try to imitate their approach.

> That's the nanny-state of programming.

So you are never activating strictures, because you don't want to be "nannied"?

Maybe time to return to assembler? ;)

> Aesthetically, at least, I am not comfortable with the "has" and friends.

Saying so I'm critical about has because it's putting the emphasis on the objects data during the design process.

An object is primarily doing something it's not necessarily supposed to have something.

It should be planned by its interface not by its state. °

update

°) See also this excellent talk

"Tadeusz Sośnierz. How Moose made me a bad OO programmer" on YouTube

Tadeusz is showing how syntax decisions are nudging programmers into designing objects leaking their internal state instead of hiding the implementation.