Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "camel casing"
-
I had a mid semester test and there was one question on how we should create class names. I was very tired, so the test started like around 9-ish. Instead of saying Camel Case method I said Camel Toe method.
Makes me wonder how did they come up with the name "camel casing" anyways?4 -
all of them. countless wasted hours.
as fate decided to turn me from $random-dev-geek into "the guy that calls the shots in tech", one of my earliest decisions was to automate formatting.
everywhere, automated at CI.
gofmt was an inspiration for the industry.
js?/ts? use prettier
C++? use ClangFormat
etc.
always default settings.
enforced by pre-commit hooks and CI.
never a single argument about bracket style, I don't care if someone likes single or double quotes better.
"fucks given" counter is fixed at 0.
everybody prefers it (ok, sometimes after a while sometimes)
of course there is still some more conventions to do for us humans.
IMHO the most critical ones.
like naming or even casing (camel, snake, kebab, - which one works where), but taking out most of the "so what" decisions takes discussions to a much more resonable level.6 -
I'm so used to camel casing variable names that when I wasn't concentrating properly just now I called a variable "outPut"1