I've been thinking about coupling for a while now. It's more than just one class or process knowing about another class or process, that happens all the time. It's about using the minimum amount of coupling in a program for it's operation. Coupling is not a 'one size fits all' issue where there is a right and a wrong way to use it. It's more of understanding when to use it, when it happens by accident and in general, being aware of the repercussions when too much coupling exists. In my mind, coupling exists when there is a specific relationship between two classes or processes. This relationship must be explicit where one class must be coupled by another into for some operation to be viable. This is not the same as just passing data from one object to another where the data couple be in the form of a third data object (a model, strings, streams, etc) where the two objects are not really bound together but there data is. This is about objects like
Just some random (isn't it all) thoughts and doings in my life.