publ;c class customer_data {
this post was submitted on 01 Mar 2024
149 points (87.4% liked)
Programmer Humor
19593 readers
507 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
I hate that the convention for naming React.useState variables is [color, setColor], rather than [color, colorSet]. After I declare 'color', I want to copy/paste that variable and append 'Set', rather than copy the variable then writing 'set' then pasting then navigating to the 4th character then flipping the case.
Granted there could be some ambiguity if there was a variable containing a unique collection (aka set) but that is far less common than declaring a useState variable. I'd even settle for appending 'SET' to quell the confusion.
One advantage of snake case is never having to remember which letters of every acronym or compound word each author decided to capitalize.
You already don't have to do that. That's what IDE's have autocomplete for.
That viewpoint makes bold assumptions about language, toolset, and preference.
It also suggests sweeping the dirt under the rug instead of not having it on the floor in the first place.
I just like to treat acronyms/initialisms as normal words. sendHttpRequest, etc.
This is the way.
snake case for everything, pascal case for struct/enum/class/trait names, and screaming snake case for constexpr identifiers is the superior method of naming. FUCK camel case, java/c# naming conventions are dumb and stupid and cringe, rust did it right
i'm in pain every time i use scala/f# or something and i have to actually interact with those HEATHEN java/c#-conformist identifiers
Apart from screaming case, which is for textual macros, i approve.
screaming snake case
What a great name for that style. Thank you.