You mean a "diff" tool these days isn't smart enough to understand non-critical differences in formatting (not things like tabs in python code)? That's pretty bad.
So what are professional teams supposed to do these days? Is it standard to have a "This is How We Write Code Here and You Better Do It This Way Or Else" rule for new hires? Is there a "Style Gateway Check" rule before code is checked into the repository?
I think NASA and "Our Code Has To Be Correct and Audited to Be Correct or People Will Die" places have rules like that, but is it common elsewhere?
Should it be? Would code jockeys put up with it? Do universities teach the importance of things like this for teams?
Thanks.
Cheers,
Scott.
So what are professional teams supposed to do these days? Is it standard to have a "This is How We Write Code Here and You Better Do It This Way Or Else" rule for new hires? Is there a "Style Gateway Check" rule before code is checked into the repository?
I think NASA and "Our Code Has To Be Correct and Audited to Be Correct or People Will Die" places have rules like that, but is it common elsewhere?
Should it be? Would code jockeys put up with it? Do universities teach the importance of things like this for teams?
Thanks.
Cheers,
Scott.