Identifying and solving Patterns is the most challenging, exciting, and
rewarding part of our jobs in my opinion.
The interesting and significant part of patterns is the design or
framework. So with the DB maintenance pattern, what does the programmer
have to do to select, add, update, and delete records? How flexible is
it? Ho you override the behavior? Additional secondary patterns often
are related such as PAGING, SORTING, VALIDATION, FIELD LEVEL SECURITY,
etc.
So in Nathan's ice cream example, how do you handle the design for:
PAGING, SORTING, VALIDATION, FIELD LEVEL SECURITY, etc?
-Paul Holm
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
