|
Steve, etal, My code has had good reviews, but they'd never pay the hours for two people. At one place the MIS Director said they had one programmer there that took care of one problem once, now get this, by *hard-coding* the actual numbers on a report that they told him the report totals were supposed to balance to. - Alan | Once, when I was working at a client in the Dallas area, a JDE _employee_ | came in to fix a problem with the invoice print program. Later, when the | program was still working incorrectly, I looked at the mods he made. Instead | of fixing the real problem, he had coded a GOTO around a block of code so | that the program would not bomb. | | This speaks to the need of having a systematic way of QA'ing programs. In | college I was taught the structured methodology and using peer reviews, the | "ego-less" approach to reviewing code. Too often the mavericks slip things | in the code that should be caught _before_ the program gets into production. | | Steve
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.