Re: Coding standards and personal choice.
David B. Harrs wrote:
So standards are forced upon people so others understand better, but those others best understand their own code, which was formatted for them.
I claim that after using a coding standard for a reasonable amount of time (one or two months), you would become used to it, and it would become your own. I used to write code with the braces on the same line as the if, and non-indented. Then I went to a company where the standard was braces on a new line, indented. It was annoying for a bit, but the editor supported it, and after about a month it wasn't a problem anymore. Now I'm at a company where the standard is braces on a new line, non-indented, and the switch to that wasn't even noticable. I don't think I'm super-flexable, or anything, but if you're writing code for eight hours a day, you'll get used to a style pretty quickly.
a) frustrate the engineer/programmer, who is an artist, and shouldn't be told how to hold his/her paintbrush
I didn't have a FreshMeat login, but this comment inspired me to get one just so that I could reply. I think that one of the main problems in the software industry is that programmers act like artists instead of engineers. If the value of being told how to hold your paintbrush is that someone else can read your programs for maintenance or debugging purposes, then that's a trade-off that everyone in this industry should be prepared, even happy, to make.
At the company I'm at now, we employ co-ops for short-term labour. The chances that they'll be around when I need to make a change to "their" code is very low, and so I am thankful that they are using the standard coding style, since it removes a large barrier to my understanding of their code.