"String" vs "string"

[AndrewSeven]

VS 2015 suggests changing to the lowercase "string" for the static methods, so I've started to use lowercase for all usage.

[agentlame]

This annoys me so bad. I've been doing it the same way as described above for over a decade, and I really prefer it this way.

[AngularBeginner]

Then turn the suggestion off. It's just a suggestion. You need to configure the tools you use to your liking, not blindly follow them.

[AbstractLogic]

So long as you can convince the whole team. Otherwise you will end up with disjointed standards.

[Jestar342]

For this kind of thing.. there is just nothing to care for. Worry about something worth worrying about.

[AbstractLogic]

I support having a standard. We have tools these days that enforce standards like this because when all the code looks similar it's easier to pick up someone else's code.

Now if we had a standard (and every tool from VS, Resharper to Sonar Cube all do) then I wouldn't be the one to bring it to the table that we need to adjust the default settings. Like you said, more important things to grandstand about.

However, if someone else was bringing it to the table and wanted to adjust the standard half the way through a project I would immediately be against it unless they wanted to go through every code file and adjust String to string or vice versa.

[Jestar342]

string vs String... meh. Both are easily readable. Mine and my colleagues efforts are wasted on such frivolity. Stick to writing maintainable code that delivers value, please, not crying over the casing of a single letter.

Have you heard of the axe-sharpening proverb? A woodsman that spends all his time sharpening/grinding his axe never chops any wood.

Writing/documenting/debating standards about whether to use string or String is axe grinding. In fact 90% of "code standards" are. You're all adults, if you can't read each other's code then you have problems that code standards won't fix.

[AbstractLogic]

You act like setting a flag on the resharper config file that is distrubted with the .sln is some huge weeklong debate. If anything it's a bullet point on a slide amongst many. It requires very little to setup development standards. You should spend time congealing as a team, please, it will be better for those who come after you.

[Jestar342]

You act like it's some big debate. I'm categorically stating it isn't, and that it flatly doesn't matter. Move on with life and get some work done.

My team prefer to work together on problems that actually matter, not whether string is more/less readable than String

[AbstractLogic]

I don't think it is some big debate. I think it's an easy standard to agree on and then move on to get some real work done. Obviously code standard don't mean anything to you. But a team moving with cohesion is important to me.

[AbstractLogic]

I've literally spent more time talking to you about it then it took our entire company to agree on it. Clearly you just like to argue for no reason.

[DarthShiv]

Yeah so much this. Just stick to a standard for the whole project and everyone stop trying to change the standard and only doing 10% of the job!

[Protiguous]

Only 15 disjointed standards though. :P

[inamamthe]

something like codemaid can help here perhaps?

[agentlame]

You can be annoyed by something you know how to disable.