202

submitted 3 weeks ago* (last edited 3 weeks ago) by [email protected] to c/[email protected]

23 comments fedilink hide all child comments

Acronyms/intialism use capital letters to encode information about words. Losing that information is a mistake. SᴍᴀʟʟCᴀᴘCᴀsᴇ is now considered a best practice.

…Or consider snake_case or kebab-case 🤷

top 23 comments

sorted by: hot top controversial new old

[-] [email protected] 102 points 3 weeks ago

ExtensibleMarkupLanguageHypertextTransferProtocolRequest

[-] [email protected] 51 points 3 weeks ago

This person Javas…

[-] [email protected] 35 points 3 weeks ago

Wouldn't that imply the existence of a ExtensibleMarkupLanguageHypertextTransferProtocolRequestFactorySingleton?

[-] [email protected] 20 points 3 weeks ago

And an AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactorySingletonBuilder!

[-] [email protected] 9 points 3 weeks ago

Sadly you can't build a singleton. AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactoryBuilder$Companion?

[-] [email protected] 9 points 3 weeks ago

80 char line maximum? I read that as minimum. My bad.

[-] [email protected] 4 points 3 weeks ago

AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactorySingletonBuilderDecoratorDelegationStrategyDispatcher

[-] [email protected] 25 points 3 weeks ago

Doing that with GNU or WINE will use your entire memory

[-] [email protected] 3 points 3 weeks ago

GNU's Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix CORE DUMP: OUT OF MEMORY EXCEPTION

[-] [email protected] 2 points 2 weeks ago

Needs more AbstractSingletonBeanProxyFactoryDefaultImplementation

[-] [email protected] 17 points 3 weeks ago* (last edited 3 weeks ago)

Acronyms/intialism use capital letters to encode information about words. Losing that information is a mistake. SᴍᴀʟʟCᴀᴘCᴀsᴇ is now considered a best practice.

…Or I dunno try snake_case or kebab-case 🤷

[-] [email protected] 8 points 3 weeks ago* (last edited 3 weeks ago)

kebab case for the win xml-http-request

[-] [email protected] 3 points 3 weeks ago

XML-HTTP-request?

[-] [email protected] 7 points 3 weeks ago

XHR boom. Sue me :)

[-] [email protected] 6 points 3 weeks ago

OP is dead now. Are you happy?

[-] [email protected] 2 points 3 weeks ago* (last edited 3 weeks ago)

Yes!

May OP request in peace

[-] [email protected] 1 points 3 weeks ago

I regret nothing!

[-] [email protected] 4 points 3 weeks ago

id throw away all of these if they aren’t struct definitions, which they aren’t.

[-] [email protected] 2 points 2 weeks ago

xhr

[+] [email protected] -14 points 3 weeks ago* (last edited 3 weeks ago)

I don't like to sticking to generalized naming conventions when autofill or intellisense is a thing. Make your names clear in whatever way you think works best, and developers still using vim can set up autocomplete using an extension or something

[-] [email protected] 22 points 3 weeks ago

Dear god please no. This way madness lies. Your idea of "whatever you think works best" is not going to line up with whatever the next person that comes along thinks, and your codebase is about to get all kinds of fucked up.

Thinking code complete is going to save you is naive. Even in languages like C and Java, where it works best, you still need to be able to read and understand the code in context. There's no hope in a language like Ruby with all it's meta programming stuff

[-] [email protected] 8 points 3 weeks ago

I'm not suggesting randomness or inconsistency, I'm saying generalizing is overkill. But you're right, "whatever works" might be taken too literal by some

You're absolutely right that depending on your autofill is not a good general approach either. Then again, you shouldn't be guessing at these either

I've worked with changing conventions in different teams. In the end people are not going to come up with some name and whether it's myOldThing or my_old_thing won't matter much. Usually I just follow whatever the team I'm working with prefers

[-] [email protected] 5 points 3 weeks ago

Yes and no. I agree that camel vs snake or that stupid mNameThing that was popular for a while, doesn't reeeeeaaally matter, although I would argue that convention over the language still has value. As an example, naming a Java variable with a capital letter would be confusing and annoying to any new devs joining the project, even if it's a valid identifier. Also it's handy to be able to look at something in ALL_CAPS and know that it's probably a static final, without having to check it's definition. I guess it's about finding that line between useful conventions and pedantry.

this post was submitted on 11 Jun 2024

202 points (94.3% liked)

Programmer Humor

31224 readers

78 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 4 years ago

MODERATORS

[email protected]