Developers who use spaces make more money than those who use tabs
661–670 of 690 posts
Re: Developers who use spaces make more money than those who use tabs
#662Earlier quoted context omitted.
> But I haven't seen a good argument for 80-character line limit other than "that's the way it's always been done." Having shorter lines makes reading diffs easier (whether it's unified, context, or split diffs). > The "official/accepted" git commit message format limits the commit message title to 50 characters, and the message body to ~80 characters. It's actually 72 characters for the commit message body for a sim…
> Having shorter lines makes reading diffs easier (whether it's unified, context, or split diffs). But is the difference that significant between 80-, 100- and (say) 120-characters wide? I personally wrap at 100 characters, I don't find that I'm fatigued by looking at diffs of the code.
Re: Developers who use spaces make more money than those who use tabs
#663This does not mean that changing from tabs to spaces will increase ones income. I would expect there simply is a confounding factor that the author did not look at. Maybe the info is not in the data. I can imagine that the space/tab choice is related to the "upbringing" of the developer. Maybe which language or editor they used first in their life. Or maybe it's related to culture. For example when using IRC, tabs ar…
Kidding aside I rather doubt anything really believes there is a causal relationship between one thing and the other.
Re: Developers who use spaces make more money than those who use tabs
#664I think it's the best of both worlds, really.
Re: Developers who use spaces make more money than those who use tabs
#665Earlier quoted context omitted.
Haskell is (slowly)growing in popularity, and F# is whitespace sensitive, and these are (for better or worse), the only languages I touch nowadays. I suppose that maybe none of the really popular languages follow this though...my bad.
Ok, here's a question I've been wanting to ask someone steeped in syntactic-whitespace languages. Do you find that two developers typing the same code will format it the same way? How much would an auto-formatter change in your team's code?
I know for a fact that an auto-formatter like `gofmt` or something would have avoided at least one argument, so it would probably would make the code better in some respects.
That said, I like the whitespace. I like that it forces you to think about how the code is formatted and it tends to make the code a lot less verbose.
Re: Developers who use spaces make more money than those who use tabs
#666Might also be that the space people, being irritatingly pedantic also include bonuses and/or stock compensation , while the tab people, always lazy and all over the place, just barfed the first number that came to mind. The answer, as always, is: lisp with parinfer - makes the whole debate irrelevant.
Re: Developers who use spaces make more money than those who use tabs
#667I needed a good laugh this morning. But of course this is pretty bogus relationship. People who drive Teslas make more money than those who drive Gremlins.
I thought the same before reading the article. But they actually tried to control for other variables (experience, country, language). If you know another variable that explains the difference please let us know.
Re: Developers who use spaces make more money than those who use tabs
#668Re: Developers who use spaces make more money than those who use tabs
#669I would like to see a similar analysis for gif vs jif pronounciation. We need to settle this.
The point is that, unlike the English "dzj" (jif) or "gh" sounds, you can pronounce a Dutch hard "g" for as long as you want to. And therefore make it louder. And therefore we will win this argument:
ggggggggggggggggggggggggggggggif!
Re: Developers who use spaces make more money than those who use tabs
#670I just like to force my preferences on other people, so I use spaces. You like 8 width tabs? Too bad, you get 4 spaces.