241–250 of 690 posts
Earlier quoted context omitted.
yeah, just because in 2017 storing source code is the most expensive thing for a company. but really, the storage is almost free nowadays...
Seems unfair to downvote you just for misunderstanding, that was sarcasm friend.
Let's move on to ASCII vs Unicode ....
Earlier quoted context omitted.
Additionnaly diff/merge tool tend to be inconsistent. So it looks good on your editor, but when I am doing your code review, alignement is totally broken. In theory, it should be easy enough to ask people to have consistent settings across all tools, but it is a bit like herding cats. Sadly most people do not even realize it could look differently without their settings. (I could ignore whitespaces when doing reviews…
Seriously? When you start on a project you configure your IDE to match the project's conventions. If you are in a mentoring role you instruct your jr developers to do the same, first thing, before writing any code. This has never been an issue at any place I ever worked. If a PM can't get their developers to do something as simple as that then you have larger organization problems than code formatted weirdly. As well…
Unless the project's settings are to use spaces.
Could it be that a few large, well-compensating employers are shifting the result? (E.g., https://google.github.io/styleguide/cppguide.html#Spaces_vs.... )
Of course, if all of the top companies are requiring spaces, then there's probably a reason for that, and its impact on salary data is thus meaningful, not just a spurious correlation.
The most confusing thing about this result is that go shows a high level of space-preferential salary difference. Go programmers who use spaces make ~20k more (at the median) than developers who don't. Only, in Go, you don't have a choice -- gofmt enforces tabs only (with spaces for alignment). So something seems odd there.
Well that settles that! We finally have proof that spaces are superior to tabs... ;)
Could it be that a few large, well-compensating employers are shifting the result? (E.g., https://google.github.io/styleguide/cppguide.html#Spaces_vs.... )
Because bigger corps generally set company wide standards on the code indentation and that more often that not prescribes spaces.