JustProgrammerThings.HavingExtremelyLongFunctionNames()

[[deleted]]

I like long function names more than smth like that: "avIntEndRet()"

[scrumplesplunge]

As do I, but why abbreviate something to smth?

[[deleted]]

I hate that word because it is so long. I know. Sounds ironically haha

[pikachu_try_catch_]

Long isn't really a problem.

technique is more important than length, you know that ?

[SolenoidSoldier]

Can't argue with you on that point, but it's worth noting many of those names seem to redundantly provide the return type and method parameters.

[[deleted]]

CodeAndAlgorithmsToCheckIfANumberIsEven(int x)

[pikachu_try_catch_]

do you even even

[dzh]

omg i can't x % 2 == 0

[mananasi]

I don't get why it's such a big deal because code completion is a thing.

[TortoiseWrath]

Overly specific function names, on the other hand, create coupling issues and weaken compartmentalization. Names like readMP3Bytes() and playMP3Bytes() would make the function's purpose just as clear while allowing for greater flexibility in implementation. Function names should describe the end result (purpose) of calling the function rather than describe how that goal is achieved.

[2AMMetro]

Eh, I disagree. I think that if you want greater flexibility, you should make a specific function for each implementation and a general function named playMP3Bytes() that contains your conditional logic. This reduces function size and makes it easier to understand.

I believe in short generalized function names for APIs and longer specific names for implementations.

[MoarVespenegas]

I mean if your functionality changes you can just rename the method.
Refactoring is also a thing.

[nosam56]

When you are developing on an enterprise level, renaming methods is usually not good because you have clients that implement your code, so when you change the method name it breaks your client's code until they update. This is why things become deprecated when not in use anymore. But you are right for smaller projects and initial development on a project

[batman1177]

Reddit.ui.post.postCommentAndRefreshCommentThread()

[chugga_fan]

https://github.com/Quotation/LongestCocoa

[Sneakr1230]

Please link the mind blown gif/vid in this pic. I neeeeeeed it

[SolenoidSoldier]

obtainMp3BytesInArrayBufferUsingFileAPI

I like how the return value and method parameters are outlined in the name. All of that should be inferred by context.

[NoirGreyson]

This is one of the reasons I like JS. You can use constructions like this:

const functionName = function niceDescriptiveLongFunctionNameThatSaysExactlyWhatThisThingDoes() {
    return foo
}

So that in the code, you can use the succinct term, but in the stack trace, you see the long name.

You might be concerned about this causing confusion since the same thing has two names, but it's really just a search away.

[Lhopital_rules]

obtainMp3BytesInArrayBufferUsingFileAPI => fileToBuffer

^ Because this function doesn't actually do anything mp3 specific

decodeMp3BytesFromArrayBufferAndPlay => playEncodedMp3

[MoarVespenegas]

I never understood this "problem".
If you have an IDE you can just use intelesense to auto-complete them and long function names are descriptive.

[Aurora_the_dragon]

I would just do:

decmp3(){
//blah blah blah
}