Many software development organizations impose coding standards on programmers, and these standards can range from general principles to very specific requirements. If you'd like to look at a more complete set of coding standards used in a major collaborative (university, government, and industry) development setting, the ACE Software Development Guidelines document, which the ACE developers use in daily practice, is a good place to start.

so?

harryobas: Many software development organizations impose coding standards on programmers, and these standards can range from general principles to very specific requirements. If you'd like to look at a more complete set of coding standards used in a major collaborative (university, government, and industry) development setting, the ACE Software Development Guidelines document, which the ACE developers use in daily practice, is a good place to start.

Well i see this as bad practise and good practise.

i have reasons as to why i say so.

Imagine you working for a firm where an in house framework is used blive me u get used to a way of programming different from the outside world. and u get stock up wen u go out there to develop for others. well to me i feel just follow a general coding standard dats mostly used in the open source world.
today i meet programmer that codes to their own way and u find it difficult going through their codes becuz its suits their own test.
note when i mean their own test i mean according to their own standards. but in reality when u ask this guys to join u on a project its gboom!!!!!!!!
disaster very baad if i may say.

I love the idea, These standards must have been designed to make collaboration painless. Developers just have to learn to adapt same way they did with the languages they use. in the long run, it pays.