Try loose coupling in your code

Ever ran into the issue of a developer making a change in the code with ripple effects?  Once that happens, you have to institute more comprehensive regression tests throughout the system, hoping to avoid such ripple effects in the future.  The Software Devotional is running a great article about loose coupling.  This is not the same as encapsulation, and while it might be more expensive on the short run, and an overkill on smallish projects, as soon as the projects get larger, it becomes very painfully obvious that a little bit looser coupling would go a long way in code robustness.  My experience certainly validates the assertions Micheal Jones makes in his article.  Give it some thought.