Re: Application Design
Re: Application Design
- Subject: Re: Application Design
- From: "Mark Hill" <email@hidden>
- Date: Sun, 1 Jul 2007 08:56:18 +0100
"Design to an interface and not an implementation" is one argument.
I've been making the fatal error of violating this rule. As a result there
has been a tendency toward over-responsiveness, Client makes the suggestion,
and I say "ok, yeah! Why not?. Spaghetti has been the result of this
approach. I've also found that the grind of implementation has restricted my
overview somewhat. I'm sure implementation is a much easier process when you
"know what your supposed to be making".
It would seem that when you have a design in place, you can discuss the
relevance of any new requests in relation to the existing design, to see if
and where it fits. Even if the client is you! This might help eliminate
"scope creep".
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden