It is my view that, when making corrections, the system should reflect what the users WANTED to happen, that the computer geek's customers are the users of the system, and the customer should be presumed to be right, in what they ask for, unless it violates some management policy.
Software fixes are great, because although it may take the programmer more 
time to set them up than one manual fix would take, over time, the time 
saved on the manual fixes tend to accumulate.
When there are multiple alternative ways available for making corrections, 
the approach that I think should be used is the one that eats the least 
amount of time, irrespective of who is doing whatever.  But that is not my 
call.
This has been how I have done my job for decades, at many different 
employers and under many different managers.
I recognize that you have a contrary view, and I will be asking my current 
managers if they agree with you or me, because over the years there has 
been some evolution in philosophy on what is appropriate.
The bank that I stick with is the one that seems most solvent, according to 
reports on banks, whose personnel behave like the customer (me) is always 
right, and I don't catch them in lots of errors.
-
Al Macintyre
http://en.wikipedia.org/wiki/User:AlMac
BPCS/400 Computer Janitor ... see
http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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 copyright@midrange.com.

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.