And the Problem is...

...fragility, of course. Let’s say that after the application has been in use for some time (long enough that you’ve forgotten the details of how it works—say a week), you discover that aDistantProperty really shouldn’t be a single property at all; it should be a collection. That’s a major change, and you know you’ll have to update all the classes that instantiate MyFriendsFriend. Ugly, but it can’t be helped.

Visual Studio has a handy tool that will help you out here; just highlight aDistantProperty and select Find All References from the context menu. But Find All References has some limitations: It won’t work across languages (what if MyClass were written in VB.NET?) or across projects that target different versions of the .NET Framework or across different solutions. A useful tool, but not perfect.