{'fraction_non_alphanumeric': 0.010854816824966078, 'fraction_numerical': 0.0, 'mean_word_length': 4.811023622047244, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
On Planning an Evaluation of the Impact of Identifier Names on the Readability and Maintainability of Programs

—One of the long running debates between program- mers is whether camelCaseIdentifiers are better than underscore_identifiers . This is ultimately a matter of programming language culture and personal taste, and to our best knowledge none of the camps has won the argument yet. It is our intuition that a solution exists which is superior to both the previous ones from the point of view of usability: the solution we name sentence case identiﬁers allows phrases as nams for program entities such as classes or methods. In this paper we propose a study in which to evaluate the impact of sentence case identiﬁers in practice.