Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: frebe73@xxxxxxxxx
- Date: 26 Jan 2007 13:12:09 -0800
You claim that it is possible to only have a few number of
getEmployeeBySomeCriteria methods with optimized SQL statements for
every different way you might need to fetch employee data? That should
only be possible for rather small applications.
Can you give an example of an application that would have an excessive
number of getemployeBySomeCriteria() methods that doesn't encroach on
becoming a report writer?
A HR application need data about employees in many different ways. RCM
already gave you one example of a very specific criteria for finding
employees. When a company needs to reduce the staff, it would be nice
if the HR application had a feature to find employees eligible for
early retirement, wouldn't it? It is easy to imagine other examples of
very specific ways of finding employees. Lets say we want to send every
manager an email containing the employees having 30-, 40-, 50-year
birthday next month. Lets say we have a function sending information to
insurance company about changes in salaries, we need a way to find
employees with changed salary. How could you possible solve this only a
few functions for finding employees?
All our reports have been implemented as
stored procedures and have been meticulously crafted to perform well and
balance to other reports. There are many similarly-named reports but
the user doesn't really see that because they navigate through the data
starting at the top-level and drilling-down.
Are there any significant difference between producing data on a paper,
displaying it on a computer screen or using it in a thread sending
e-mails? I have seen systems like you describe above. The only way to
access a lot of the information was to print it, or get it as a large
PDF-file. It so 60's.
If there really was a requirement for ad-hoc getEmployee() methods
What's ad-hoc about set theory and predicate logic?
Fredrik Bertilsson
http://mybase.sf.net
.
- Follow-Ups:
- References:
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: JXStern
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: topmind
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Robert Martin
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: topmind
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Robert Martin
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: frebe73
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Robert Martin
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: frebe73
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Robert Martin
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: frebe73
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- From: Thomas Gagne
- Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- Prev by Date: Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- Next by Date: Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- Previous by thread: Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- Next by thread: Re: Critique of Robert C. Martin's "Agile Principles, Patterns, and Practices"
- Index(es):
Relevant Pages
|