If you're referring to two different local variables of two different functions, then obviously that is the case, and the change in the styles shouldn't matter, as they are in fact two different variables.
Well I would actually say that changing variable names simply because they don't comply with the standard isn't only a productivity issue. It is bad practice and a productivity issue. I would want the diff to show the change for two reasons. 1. it isn't a trivial change to change a variable name like it is to change whitespace. This can introduce bugs. 2. the productivity issue.
I would also say that I would never, ever, ever use an IDE which would change the actual variable names and not just the whitespace. Bill sounds like he needs to attend anger management if a style change makes him angry.
Well my argument to man of mister e and first reply to Decameron are two different arguments.
My argument to man of mister e, was simply to imply that using features in your diff program can help you ignore meaningless differences in styles.
My argument to Decameron was in reply to his blanket statement that "the reason why coding styles exist is that they increase the readability of your code." This is an absolute statement about the nature of coding styles, which is factually incorrect, as I have demonstrated by personal experience as well as well known failures from the daily wtf.
I don't disagree that there needs to be at least some level of tracking (usually the kind inherent in most source control software). As stated in another reply, understanding the programmers original logic can greatly help things. I agree that it can also help you find the source of malicious code.
Brace position and spacing both are encompassed by the whitespace argument that I was referring to. Also I would say that if you have a programmer who chooses to change the variable names of their inherited code simply because it doesn't conform to the standard, then I would say you have more to worry about than coding style.
I'm not seeing the issue. If a dude is changing variable names, then I would want to know about it as that is less trivial than whitespace changes.
This seems like another productivity issue. If I have a guy focusing on changing variable names from myVar to my_var, then he's either going to be talked to and told to wisen up or canned as he's not doing anything productive.
And you're missing my point when I say that just because a particular style is standardized doesn't mean it produces self-documenting code. If the person in charge of setting the standard is an incompetent programmer to begin with, then his standard could introduce confusion. There are many examples of this happening on the daily wtf. And in fact, I have had managers that have tried to enforce standards which would turn my code from easily understandable to a mess of variable acronyms.
To a competent programmer, stardards are more of a guideline. Any good coder knows how to produce clear and maintainable code, and should be able to read similarly clear code even if the case of the variables are different or there is an endline after the curly braces. Bad coders need and cling to these rules, however, because without them they would literally have no idea what to do.
Sorry, it was your wording in your original statement which made me assume that you were talking about this horrible practice. I definitely agree that knowing who originally coded something in order to find out their logic is extremely important, especially for those little bugs, just have a horrible aversion of people on my teams pointing fingers at each other instead of actually doing their jobs.
His first point was clearly addressing the differences in whitespace. Any moron complaining about whitespace in code doesn't really belong in coding. Diffs can and should ignore whitespace (unless you're talking about languages that don't ignore it), so his point was moot. And I personally have enough experience to know exactly what he is talking about
Assigning blame to people because of bugs is in fact one of the most detestable things you can do in software development. Bugs will always exist, no matter what coding style you use. If your first priority is to name and shame and not fix the code and move onto the next issue, then your teammates are going to hate you.
Not sure if you are being serious with your point or not due to your case changes, but I will bite.
Just because a style is standardized doesn't mean your code is more readable using that style. In fact a lot of the styles expected of me made my code less clear, and when I chose to ignore them, my code was never touched in code reviews, because everything was clear and intuitive without conforming directly to the style.
If you personally like clear / readable code, then no standard will ever be a replacement for you.
Personally if you have a coder using myVar and my_var for two different variables in the same code, I think you have more to worry about that coding style.
Agreed, it seems counter-intuitive to allow Microsoft to continue to dominate the PC Gaming OS when they already have vested interest in a completely different platform.
What is safe and secure? I don't think anyone will agree on the complete definition of this. The government will have its definition. The MPAA/RIAA will have their own definition. I as a hacker have my definition. I prefer the way the internet is, because I can make it as safe or as unsafe as I choose. I don't need anyone else to define those terms for me.
Slashdot Mirror
Who are you referring to?
I saw two arguments from the first guy, and I addressed both of them.
If you're referring to two different local variables of two different functions, then obviously that is the case, and the change in the styles shouldn't matter, as they are in fact two different variables.
Well I would actually say that changing variable names simply because they don't comply with the standard isn't only a productivity issue. It is bad practice and a productivity issue. I would want the diff to show the change for two reasons. 1. it isn't a trivial change to change a variable name like it is to change whitespace. This can introduce bugs. 2. the productivity issue.
I would also say that I would never, ever, ever use an IDE which would change the actual variable names and not just the whitespace. Bill sounds like he needs to attend anger management if a style change makes him angry.
You assume incorrectly. This is common sense.
Well my argument to man of mister e and first reply to Decameron are two different arguments.
My argument to man of mister e, was simply to imply that using features in your diff program can help you ignore meaningless differences in styles.
My argument to Decameron was in reply to his blanket statement that "the reason why coding styles exist is that they increase the readability of your code." This is an absolute statement about the nature of coding styles, which is factually incorrect, as I have demonstrated by personal experience as well as well known failures from the daily wtf.
I don't disagree that there needs to be at least some level of tracking (usually the kind inherent in most source control software). As stated in another reply, understanding the programmers original logic can greatly help things. I agree that it can also help you find the source of malicious code.
Brace position and spacing both are encompassed by the whitespace argument that I was referring to. Also I would say that if you have a programmer who chooses to change the variable names of their inherited code simply because it doesn't conform to the standard, then I would say you have more to worry about than coding style.
I'm not seeing the issue. If a dude is changing variable names, then I would want to know about it as that is less trivial than whitespace changes.
This seems like another productivity issue. If I have a guy focusing on changing variable names from myVar to my_var, then he's either going to be talked to and told to wisen up or canned as he's not doing anything productive.
And you're missing my point when I say that just because a particular style is standardized doesn't mean it produces self-documenting code. If the person in charge of setting the standard is an incompetent programmer to begin with, then his standard could introduce confusion. There are many examples of this happening on the daily wtf. And in fact, I have had managers that have tried to enforce standards which would turn my code from easily understandable to a mess of variable acronyms.
To a competent programmer, stardards are more of a guideline. Any good coder knows how to produce clear and maintainable code, and should be able to read similarly clear code even if the case of the variables are different or there is an endline after the curly braces. Bad coders need and cling to these rules, however, because without them they would literally have no idea what to do.
Sorry, it was your wording in your original statement which made me assume that you were talking about this horrible practice. I definitely agree that knowing who originally coded something in order to find out their logic is extremely important, especially for those little bugs, just have a horrible aversion of people on my teams pointing fingers at each other instead of actually doing their jobs.
His first point was clearly addressing the differences in whitespace. Any moron complaining about whitespace in code doesn't really belong in coding. Diffs can and should ignore whitespace (unless you're talking about languages that don't ignore it), so his point was moot. And I personally have enough experience to know exactly what he is talking about
Assigning blame to people because of bugs is in fact one of the most detestable things you can do in software development. Bugs will always exist, no matter what coding style you use. If your first priority is to name and shame and not fix the code and move onto the next issue, then your teammates are going to hate you.
Not sure if you are being serious with your point or not due to your case changes, but I will bite.
Just because a style is standardized doesn't mean your code is more readable using that style. In fact a lot of the styles expected of me made my code less clear, and when I chose to ignore them, my code was never touched in code reviews, because everything was clear and intuitive without conforming directly to the style.
If you personally like clear / readable code, then no standard will ever be a replacement for you.
Personally if you have a coder using myVar and my_var for two different variables in the same code, I think you have more to worry about that coding style.
Most diffs can ignore whitespace...
I don't understand your second point.
Agreed, it seems counter-intuitive to allow Microsoft to continue to dominate the PC Gaming OS when they already have vested interest in a completely different platform.
What is safe and secure? I don't think anyone will agree on the complete definition of this. The government will have its definition. The MPAA/RIAA will have their own definition. I as a hacker have my definition. I prefer the way the internet is, because I can make it as safe or as unsafe as I choose. I don't need anyone else to define those terms for me.
Well for an ideal exploit, you wouldn't know.
"being"
I am surprised to find out that this is not due to it be the front of some sort of energy company that gets energy from baby seal pelts.
So tell us all about your vast experience that informs your scholarly opinion.
The difference being that you have to manually configure those instead of programmatically using their API.
Someone manually configuring load balancers isn't being a developer. They are being a system administrator.
it was a joke, you useless cunt.
Metro is the name that has to change not SkyDrive.
The Mythbusters proved that you CAN actually polish a turd.
Oh wait I guess this isn't that unrelated.