Once you know where the separations among modules should be, obey those separations religiously. That includes making a conscious effort to keeping the code isolated, using naming conventions that facilitate the separations, and so forth. Every subsystem is an empire looking to extend its sphere of influence well beyond where it should, and if you don't watch out, they'll succeed. To me, good code is not a matter of specific naming conventions, the algorithms used or other tricks. That's clever code, not necessarily good code.
Good code is all in the connections, how well the code is structured and organized.
And in the end, that all boils down to these little Pandora's Boxes. Many programmers just don't seem to realize it. Java has a similar layout, along with package encapsulation. While many subsystems can have massive and complicated implementations, the best interfaces are those that are simple and to the point. And they should be clear what they're interfaces to.