I don’t (brain processes the photons bouncing off the object and colliding with the cones and rods in the retina) a problem with this.
(See what I did there?)
(I think I met my dad joke quota for the month.)
The curse of camel case!
PascalCase
I mean, this is overdoing it a bit and the “thisVarMakesItSoThat” part is redundant, but other than that those are very descriptive property- and method names, which is not a bad thing.
Aah… Like reading a novel. But with a lot of weird punctuation… Or maybe just like a novel then.
Looks ugly until you need to implement something and realize you’ve been blessed with a description of business logic.
Strong names are great, but (sometimes) mentioning the type of variable in the name is redundant.
Wtf. It’s not even center aligned.
“Commenting is for n00bs”
String if_you_must_please_at_least_separate_the_words
You forgot to declare custom primitive types. You cannot create a bool you gotta declare a
DoubleYouDoubleYouDoubleYouDotLemmyGradDotML_BoolI’m already annoyed by the end of
public static final stringthat the variable name doesn’t even bother me in these sorts of langauages. All things should be public, static, & final, by default so they aren’t necessary to write. You should only have to write what unsafeties you are opting into.this is a crime against humanity
