Re: coding standards

["Dan Ritter-2" <user=13@nabble.blu.org>]

 On Thu, Jun 05, 2008 at 08:04:04AM -0400, Stephen Adler wrote: 
> What are common coding standards (or web pages discussing the issue?) 
> 
> I'm working with a group of coders and I need to impose some kind of 
> sensible coding standards... 

1. You must have a spec. 
 (What's the point otherwise? If you don't know what the code is 
 supposed to do, it doesn't matter what it does do.) 

2. Your code must work. 
 (See point one.) 

3. Your code must be comprehensible by other people. 
 (You will be a different person a year from now when you look 
 at this code again. Write clearly.) 

4. You must test against the spec. 
 (If you haven't tested and resolved the issues, you haven't 
 done your work.) 

5. You must all use the same versioning system. 
 (If you don't see this immediately, there might not be any hope 
 for you in the computer industry. Try marketing.) 

6. You must have a process for dispute resolution. 
 (So everyone can know what's going on.) 

I think that's most of it. Just about everything else is 
negotiable. 

-dsr- 



-- 
http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference. 

When freedom gets lots of exercise, it protects itself. 

-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean. 

_______________________________________________ 
Discuss mailing list 
[hidden email] 
http://lists.blu.org/mailman/listinfo/discuss