On Monday, 02/04/2002 at 09:47 EST, Norman Bollinger <[EMAIL PROTECTED]> wrote: > Its a matter of programmer discipline and management follow through. When I > write a message I know > why I am writing it and what it means. It only takes a minite or two to > document that at that moment. If my boss allows me to skip the > documentation at that time then we both have failed. But if he catches me > then we are successful. > > My most successful attempt at reasonable documentation required that a > peer of my choice reviewed my code which also required message > documentation in the front of the program. The programmer's designed that > system and it worked well. > > Its simple slop versus discipline.
I agree, Norman. If fact, a peer review of command syntax, messages, and return codes can reveal design flaws and inconsistencies that are not obvious from reading code, esp. when the code is complex. Sometimes it just isn't obvious until you see it in print, the way a customer will see it.... Regards, Alan IBM Senior Software Engineer z/VM Development, Endicott, NY Phone 607.752.6027 fax 607.752.1497 t/l 852
