A Casing Style So Unholy It Scares the Devil
Description
A meme depicting a humorous dialogue between Satan and a person condemned to hell. The text exchange goes: 'Satan: So what are you in hell for?', 'Me: Because of my casing style', 'Satan: Can't go to hell because of casing style', 'Me: here_lOOk-At_it'. Below this text, an image shows a cartoon depiction of a red, horned Satan looking utterly horrified, disgusted, and recoiling in shock. The joke centers on programming 'casing styles' - the conventions for writing variable and function names (e.g., camelCase, snake_case). The example 'here_lOOk-At_it' is a programmer's nightmare, an anarchic mix of snake_case, random capitalization, and even a hyphen, which is often illegal in identifiers. For experienced developers, who prize readable and maintainable code, this is a cardinal sin. The humor lies in the exaggeration that this coding practice is so abominable that it repulses even the lord of evil, validating the developer's own visceral reaction to such poor code quality
Comments
10Comment deleted
I've seen code that needed a debugger, code that needed a profiler, but this is the first time I've seen code that needs an exorcist
here_lO0k-At_it: a cross-language DoS - ESLint, clang-tidy and Flyway all segfault while the architecture guild schedules yet another “naming-convention summit.”
The only thing worse than this naming convention is explaining to the junior dev who inherits your codebase why the production database has columns named like 'user_ID', 'UserId', and 'USER-id' all referring to different things
The real hell isn't the mixed casing style itself - it's realizing this passed code review, made it to production, and now you're the one who has to maintain it. At least Satan has the decency to look horrified; your tech lead just approved the PR with 'LGTM.'
Satan's favorite escape sequence: \u{1F525} for casing so hellish, even the linter demands a rollback
We had JSON camelCase, Postgres snake_case, CSS kebab-case, and Go demanding PascalCase - by the third adapter we called it CaseOps and accidentally created a Tier‑1 microservice with a 99.99% SLA
here_lOOk-At_it is the rare identifier that violates PEP8, Go’s MixedCaps, and ESLint’s naming-convention at once - turns into subtraction in Bash - and even Satan can’t approve that PR
Yes, of course snake-camel-kebab-case Comment deleted
😂😂😂 Comment deleted
Typical c++ Comment deleted