> The kinds of things I am referring to include (off the top of my head): > > - SoC (What does a concern look like? How much separation is enough? Etc. > ) > - The "proper" design of URLs (.../cocoon1 vs. .../cocoon/old vs. ...) > > <grumble> > People on this list do step in and say "this is mixing concerns" and "that' > s not a proper URL". This is a good thing for Cocoon. However, to > paraphrase, "Tell a developer not to do something and you fix the current > implementation/design. Teach them how to recognize good and bad things, > and you fix all future implementations/designs." I want to learn, damnit! > </grumble>
<fwiw role="general"> What takes longer to come to boil in a microwave oven: - a cup of water heated for 1 minute and 10 seconds, or - a cup of water heated for 1 minute and 11 seconds ? If there was no user interaction the answer is easy, but since we are dealing with an interface that humans must deal with the correct answer is 0:01:11. This is because it is faster/easier for the user to hit the "1" button three times rather than for them to search for the "0". </fwiw> My point being, if the interface slows the user down then the optimaztions are useless. best, -Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
