camelCase versus under_scores

hwayne / awesome-cold-showers

For when people get too hyped up about things

Other

7.26k stars 82 forks source link

camelCase versus under_scores #20

Closed technosophos closed 1 year ago

technosophos commented 4 years ago

[X] I have followed the code of conduct.
[X] I have followed the contributing guidelines and used the proper item format.
[X] This is not a duplicate.
[X] The resource is free.
[X] The resource is rigorous because: (please list) Two academic papers are cited, both published in respected journals.
[X] The resource is not obnoxious, condescending, etc.
[X] My writup is respectful of both sides.
[X] I've added reasonable caveats.
[X] I've noted if the resource is a video, pdf, etc.

This is what makes your repo fun: I was going to post the Binkley article, and then discovered the newer Sharif article and learned something new!

hwayne commented 4 years ago

Oh my god this looks amazing.

The writeup looks good. I want to read through the paper before merging, though.

hwayne commented 4 years ago

Okay read it, two important caveats that should be added:

The sample size was only 15 people.
"Subjects were historically trained mostly in the underscore identifier style and were all programmers. "

I also think the information that this is a replication should be moved from "Caveats" to "Notes". It's not information that changes the strength of the paper's findings.

jab commented 4 years ago

Kind of surprising to see the style referred to as "under_scores" rather than snake_case. Worth renaming this "camelCase vs. snake_case" (despite the paper's title)?

politician commented 2 years ago

Those caveats though!

Does it still make sense to be included here?

Edit: Also before people go off hyping snake case must be used everywhere, should it be added to the notes that one should always seek for existing conventions in their framework/language of choice?

fabianschwarzfritz commented 2 years ago

I have been following this for a while. I doubt a "study" with a sample size of 15 people should be used to derive conclusions about what's better.

The sample size is way to small, this should not be merged.

hwayne commented 1 year ago

Guess who didn't get any updates that you made changes!

Me!!!

hwayne commented 1 year ago

I have been following this for a while. I doubt a "study" with a sample size of 15 people should be used to derive conclusions about what's better.

The sample size is way to small, this should not be merged.

I agree that it's too small to derive any conclusions from, but it's still more work than was put into "Microservices" and "Agile Methods", both of which I added. Also, I really like the work @technosophos put into it. I'll merge this for now but make a note that we might have to schism much later into "rigorous" and "non-rigorous" stuff.