CodeQuality
Post #3669 · source on Telegram
When your variable name violates every style guide at once
Description
The image shows a dark themed code editor window with rounded corners and three macOS traffic-light buttons (red, yellow, green) in the top-left. Centered in the editor is a single JavaScript line: “const vARIABLE_nAME = '';”. The keyword “const” is syntax-highlighted in muted blue, while the variable identifier is a chaotic mix of lowercase, uppercase, and an underscore, instantly clashing with any sane camelCase or snake_case convention. The snippet humorously captures the nightmare of inconsistent naming conventions that senior devs battle during code reviews and the inevitable linter complaints about readability and maintainability
More like this
More like this in CodeQuality →
Use J and K for navigation
Comments
21Comment deleted
Pretty sure this variable was named by an argument merge between Prettier, ESLint, and a Friday-afternoon intern git-revert
After 20 years in the industry, I've seen microservices become nanoservices, watched Kubernetes eat the world, and survived three JavaScript framework apocalypses - but I still spend 30 minutes debating whether it should be getUserById, fetchUserWithId, or retrieveUserUsingIdentifier, only to ship it as temp_user_thing and promise myself I'll refactor it later
When your junior dev asks 'what naming convention should I use?' and you reply 'yes' - this is what you get. It's like they ran every style guide through a blender and picked the chunks that survived. The real tragedy? This would pass the compiler but fail every code review from here to eternity. At least they used const instead of var, so there's that one redeeming quality in this monument to chaos
'LGTM except rename VARIABLE_NAME' - the code review comment that unites juniors and grizzled architects alike
vARIABLE_nAME: where Prettier shrugs, @typescript-eslint/naming-convention throws a fit, and the rest of the sprint becomes a bikeshed on consistency at scale
We spent a week bikeshedding the naming convention and still shipped Hungarian_snakeCamelCase; turns out const guards values, not institutional memory
Nice meme sir Comment deleted
dEV-mEME Comment deleted
emem_ved Comment deleted
good morning to everyone except the guys who do this Comment deleted
Is overscore allowed in identifiers? Comment deleted
No Comment deleted
You may also add sex pose number you were at, when you decided with it's naming, to variable name. Comment deleted
... in Roman notation. 🧐 Comment deleted
Please remember that's also reversed according to the case style. Comment deleted
Since any Roman numeral constitute a totally valid identifier, then why bother with meaningful prefixes for them? i iI iII iV v vI ... Say goodbye to i, j, k - that's way too mainstream! Comment deleted
But you need to take care of the reversed IV, don't you? Comment deleted
It's someone else's job to read and understand the code! Comment deleted
Disgusting Comment deleted
I personally prefer mOcK-dAsH-cAsE Comment deleted
This is beyond cursed Comment deleted