Re: What databases have taught me
From: Robert Martin <unclebob_at_objectmentor.com>
Date: Fri, 30 Jun 2006 20:33:15 -0500
Message-ID: <2006063020331564440-unclebob_at_objectmentorcom>
Date: Fri, 30 Jun 2006 20:33:15 -0500
Message-ID: <2006063020331564440-unclebob_at_objectmentorcom>
On 2006-06-28 22:20:57 -0500, "topmind" <topmind_at_technologist.com> said:
> Like I said elsewhere, most coupling examples I've seen make
> assumptions about which change path is the most likely. The ones you
> choose are not the most likely in my experience (at least for my
> domain). Thus, your "coupling" metric is not a slam-dunk free lunch. It
> makes assumptions that some of us question. In short, technical people
> will disagree about what decoupling option is the best, since they may
> conflict.
However, very few people disagree that decoupling is important. And, using OO, you can do a lot of decoupling.
Decoupling is not a free lunch. It *is* an important tool.
-- Robert C. Martin (Uncle Bob) | email: unclebob_at_objectmentor.com Object Mentor Inc. | blog: www.butunclebob.com The Agile Transition Experts | web: www.objectmentor.com 800-338-6716 |Received on Sat Jul 01 2006 - 03:33:15 CEST