Studies show CamelCase is easier to type, which is what the book references. But, studies also show that snake_case is easier to read.
Code will be read more than it will be written, so it should be optimized for the reader.
Code will be read more than it will be written, so it should be optimized for the reader.
I vote for kebab-case, but I didn't find any study where it was included...
But I'm eager to find counter examples.
> Results indicate that camel casing leads to higher accuracy among all subjects regardless of training, and those trained in camel casing are able to recognize identifiers in the camel case style faster than identifiers in the underscore style.
What does it mean:
> those trained in camel casing are able to recognize identifiers in the camel case style faster than identifiers in the underscore style.
It is not normal if you train in reading something => you are good in recognizing that things that you are trained than something else than you did not train for?
If anyone has access to the study, how many among 135 are programmers that were trained in camel case and how many in snake case?
Seems like it should be shift+space inserts a variable-split-token and different editors can display it as a - _ or caps of the next character as desired. Like tab characters being configurable as a number of spaces.