Mainly because you'll never get everyone to agree what the one naming
convention will be. The question is where are you having your trouble? Code
formatting and naming is a little tricky, and there are a few rules that you
should follow(generally those in the .NET guidelines), but internal and
private code is mostly up to the developer, although it should be kept the
same across a project(and organization is applicable).
Code
formatting and naming is a little tricky, and there are a few rules that you
should follow(generally those in the .NET guidelines), but internal and
private code is mostly up to the developer, although it should be kept the
same across a project(and organization is applicable).
You know, _I'm_ willing to adopt *any* sane naming convention, just to
keep to standards. I just get annoyed when reading through someone
else's code and seeing that they haven't made an effort to keep with
the relevant guidelines/standards.
In my view, so long as the standard is /sane/, programmers can adapt
to it, no matter what they're accustomed to.
You know, _I'm_ willing to adopt *any* sane naming convention, just to
keep to standards. I just get annoyed when reading through someone
else's code and seeing that they haven't made an effort to keep with
the relevant guidelines/standards.
In my view, so long as the standard is /sane/, programmers can adapt
to it, no matter what they're accustomed to.
I'm sure they can, its more a matter of convincing them they should, . I
am only really anal about external interfaces, I rarely worry about the
state of the private code(although, even with bad code formatting and naming
conventions, when I'm modifying that code I make an effort to make the same
choices and use the same naming pattern). Its a frustration, but it can be
lived with.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.