From: Intransition <transfire@...>
Date: 2011-11-22T07:00:24+09:00
Subject: Re: Principle of Best Principles

------=_Part_1212_20018423.1321912821181
Content-Type: multipart/alternative; 
	boundary="----=_Part_1213_32911577.1321912821181"

------=_Part_1213_32911577.1321912821181
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

As it turns out you (and others) are pretty spot on, though I'm not sure 
the n:1 relationship is necessarily the best way to think about it, it did 
provide a good starting point. But the "too loose coupling" is really the 
great point here. And that's something you don't often hear!!! We always 
here about over-coupling. But really it's "just right coupling" that is the 
real deal.

So in my (real life) case I kept the coupling.

However, I did end up applying the Single Responsibility Principle, and 
though it was bit difficult to work out the restructuring as first, the 
code turned out much cleaner in the end. So that pattern at least proved 
itself.

Lessons learned.

Thanks.

------=_Part_1213_32911577.1321912821181
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

As it turns out you (and others) are pretty spot on, though I'm not sure the n:1 relationship is necessarily the best way to think about it, it did provide a good starting point. But the "too loose coupling" is really the great point here. And that's something you don't often hear!!! We always here about over-coupling. But really it's "just right coupling" that is the real deal.<br><br>So in my (real life) case I kept the coupling.<br><br>However, I did end up applying the Single Responsibility Principle, and though it was bit difficult to work out the restructuring as first, the code turned out much cleaner in the end. So that pattern at least proved itself.<br><br>Lessons learned.<br><br>Thanks.<br>
------=_Part_1213_32911577.1321912821181--

------=_Part_1212_20018423.1321912821181--