Although i am a 4th year (although haven't started this
actual year yet) Software engineer, with little real world experience (at the moment) i'd imagine that on large scale or massive scale software projects that you'd need some pretty tight configuration management in order to keep track of everything.
The main point of coding standards is for code quality; maintainability/readibility and uniformity. Basically, when others are going to be looking through your code, to either debug/review or maybe extended it (extending code beyond it's original function/purpose can be dodgy though
) it makes it
a lot easier if everything is the same style to what you've been doing before. For once, individuality and uniqueness isn't really a good thing
Quote:
KnifeMissle
There is so much about writing software to concern yourself with and this is simply not one of them
|
If you learn writing code, with a coding standard in mind, it becomes second nature to you and you probably don't need to
concern yourself with it anyway. Although i imagine that each company has small little nitpick differences between styles (which could be a little pedantic).
getting to preincrementing now, you're right in saying that you shouldn't use it in combination with anything anyway, but if someone does, it (well i think) it's unintuitive. Although as nonsensical said, if s/he's just writing the code for themselves, knowingly what's happening the maybe it's ok? It's hard to say what'd be (un)intuitive for others i guess...
and sorry for the threadjack
