Not sure what you mean exactly, but I think I have some idea:
publicstaticboolIsValid(thisEntityentity){// force tab indent to hereif(entity.IsActive&&entity.Expires.Date<=Datetime.Now().Date){returntrue;}else{returnfalse}}
In which case, if you aren't used to working on teams, I can get the frustration. I assume you don't like that whitespace format? But above that is the "correct" format for C# according to MS, expect I used spaces instead of tabs.
Consistency across teams (I currently have peers around the globe) being able to scan code quickly, and not mess with a dozen styles is actually critical. So for me, an IDE that does well with something like StyleCop, linters, Resharper etc. is a very nice to have.
Especially for Jr. developers: "Here's the MS recommended style, here are our exceptions".
I always try to keep the list short, because no one wants to miss a sprint because someone kept flagging " needs work" for minor style issues.
I'm Calin Baenen – AKA KattyTheEnby – a programmer born October 30th, 2006.
I love programming, it has been my passion since I was a kid, and will forever be my passion.
Comments, in general? Or comments similar to that?
I'm of the camp: Comments should explain what your code can't.
/// 3rd party library has a "bug" which requires this format
If you mean: Using that style of commenting for a single line of comments, then:
1) Almost every style guide I've seen would call that a bad practice. It should be fixed
2) In compiled languages, at least it has no impact as generally the compiler will drop comments.
I'm Calin Baenen – AKA KattyTheEnby – a programmer born October 30th, 2006.
I love programming, it has been my passion since I was a kid, and will forever be my passion.
Not sure what you mean exactly, but I think I have some idea:
In which case, if you aren't used to working on teams, I can get the frustration. I assume you don't like that whitespace format? But above that is the "correct" format for C# according to MS, expect I used spaces instead of tabs.
Consistency across teams (I currently have peers around the globe) being able to scan code quickly, and not mess with a dozen styles is actually critical. So for me, an IDE that does well with something like StyleCop, linters, Resharper etc. is a very nice to have.
Especially for Jr. developers: "Here's the MS recommended style, here are our exceptions".
I always try to keep the list short, because no one wants to miss a sprint because someone kept flagging " needs work" for minor style issues.
Well, things like this are annoying, too.
Comments, in general? Or comments similar to that?
I'm of the camp: Comments should explain what your code can't.
If you mean: Using that style of commenting for a single line of comments, then:
1) Almost every style guide I've seen would call that a bad practice. It should be fixed
2) In compiled languages, at least it has no impact as generally the compiler will drop comments.
No, I meant w/ doc-comments, it forces me to have a space on all (comment) lines below the start, yet doesn't align the top (starting) line.
Refer to what I sent in the code block to resolve any questions, and ask you're still confused.