We don't really work in a vacuum. There are some defacto standards out there. C code is not portable. It must be made or written in special ways. The best coding I have ever done had good and reasonable documentation too. And the worst had none.
On Mon, 4 Feb 2002, Post, Mark K wrote: > Excuse me? "Management follow through?" Management could be us - their peers. Norman Just who do you think is managing > the hundreds/thousands of Open Source developers in the world? > > Mark Post > > -----Original Message----- > From: Norman Bollinger [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 04, 2002 9:48 AM > To: [EMAIL PROTECTED] > Subject: Re: Messages Manual > > > 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. > > Norman >
