On Fri, Jun 18, 2010 at 09:50, Joe Sondow <[email protected]> wrote: > In a complex > application there may be lots of tables and associations that help the > developers maintain state correctly, but which are just a bunch of > noise to the user and can even omit relevant details that the user > needs to know.
Sure, looking into detail there might be a lot of differences between DB/architecture and UI. In reality when I was taking that rule of thumb into doubt, I was thinking more general, such as if I have a DB with companies and contacts, why should it then be wrong if I can see the company-contact linkage also in the UI directly. I think that was my missunderstanding of that particular critic of software design. The date and period sample given by Kevin was a simple and good one and even you pointing out internal structures that might be there for performance reasons but be presented in a different manner to the user. I think I understand now. Thanks. -- Martin Wildam -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
