FaggotCase vs lowercase_underscores

If you aren't using lowercase_underscores (or lowercase-hyphens for you schemers) you're doing it completely wrong. PascalCase/camelCase aka JewCase identifiers take between 0.5-1.0 seconds longer to visually parse and identify.

http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=5521745&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D5521745
http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=5970159&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D5970159
http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=5970176&navigation=1
http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6240505&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6240505
http://whathecode.wordpress.com/2013/02/16/camelcase-vs-underscores-revisited/
https://whathecode.wordpress.com/2011/02/10/camelcase-vs-underscores-scientific-showdown/

but TL;DR
lowercase_underscores : http://www.youtube.com/watch?v=_jXKIy_2p5U
NiggerCase : http://www.youtube.com/watch?v=0itOCgJtNVU

>>1
They have names:
https://en.wikipedia.org/wiki/Camelcase
https://en.wikipedia.org/wiki/snake_case

>>3
I was going to say this: [requesting source]
But I found your source:
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.158.9499&rep=rep1&type=pdf
7 Summary and Future Challenges
The study described in this paper shows that although
those without training take longer to recognize identifiers in
the camel case style, all subjects are more accurate when
identifying a camel-cased identifier. In addition, subjects
trained to use camel casing take less time to identify a
camel-cased identifier than an underscore identifier.
The next step is to consider higher-level tasks in more
realistic settings. One task would investigate the impact
of camel casing versus underscores when reading blocks
of code. For example, subjects might be asked to search
for a particular identifier. Another task would ask subjects
to read natural language para
graphs modified to use camel
casing or underscores. This would enable more direct com-
parisons with previous work done in psychology such as
Epelboim et al. [6].

IOW: Biased as fuck. Even "5.4 Threats to validity" section proof the point. My personal style is always the COBOL_WITH_UNDERSCORE_CONVENTION, making VARIABLES incredibly unambiguous as to what a var SHOULD = as. functions_left_to_reader(), however ᴛʜɪꜱ_ɪꜱ_ꜰɪɴᴇ_ᴛᴏᴏ().

FUNCTIONS_SHOULD_NOT_BE(int like_this, char* at_all);
it_just_looks_wrong(int SINCE_THE_VARIABLES, char* HAVE_GREATER_IMPORTANCE);
SeeIfICare(int ThatYouCanRead, char* ThisAtAll);
ItJustMakeIt(int confusing_as_hell, char* when_you_change_conventions);
data_has_higher_value(int ThanTheProcedures, char* ThatCallThem);