Chromatic understands (i'm sure) that you don't care about code formatting. That is far from the point. The point was that if you have team codeing standard then all team members need to conform to them. The importance of team coding standards is that all code is easily readable by all members without having to make adjustments to coding standards. Your analogy with all wearing the same clothes just doesn't fit because cloths have nothing to do with other members being able to *easily* read your code, while code formatting does. I say *easily* because obviously they will be able to read it as long as they understand perl, the point is to make it so that each member isn't constantly trying to readjust to the next persons code formatting.
| [reply] |
My point is that these standards can be "enforced" by a script that reformats my ugly code. After that my ugly code will be nice looking and everyone will understand it and everyone will be happy. Even me.
What he does not understand is, that I feel a hinderance in having to follow such guidelines by hand. That's all I said in the last X downvoted postings.
The analogy to clothes does fit for me. Having to follow guidelines that don't fit for me is like having to wear a tie all day long at work. It simply won't fit and I won't be as productive as I would be, wearing casually clothes.
s$$([},&%#}/&/]+}%&{})*;#$&&s&&$^X.($'^"%]=\&(|?*{%
+.+=%;.#_}\&"^"-+%*).}%:##%}={~=~:.")&e&&s""`$''`"e
| [reply]
[d/l]
[select] |
My point is that these standards can be "enforced" by a script that reformats my ugly code. After that my ugly code will be nice looking and everyone will understand it and everyone will be happy.
That's nice, but it does absolutely nothing to help when you and another developer need to code together. In that case, you're asking him or her to be familiar reading two styles of code, the team standard and your own personal standard.
Or do you suggest that asking you to work with your team members occasionally is also a hindrance?
| [reply] |
| [reply] |
