A Casing Style So Bad, Not Even Hell Wants It
Description
The meme is a dialogue-based joke followed by a reaction image. The text describes a conversation: '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. Satan:'. The final line is followed by an image of a cartoon devil, red with horns, looking utterly horrified and repulsed. The humor comes from the programmer's 'casing style,' which is a chaotic mix of snake_case, camelCase, and random capitalization (`here_lOOk-At_it`). This is a major violation of coding best practices, which emphasize consistency for readability and maintainability. The joke is that this coding sin is so egregious that it disgusts even Satan, the embodiment of evil, making it a relatable and funny scenario for any developer who has encountered inconsistent and messy code
Comments
8Comment deleted
I once inherited a codebase with mixed casing like that. We didn't refactor it; we put it behind a VPN and charged archeologists to study it as a digital atrocity
Mix snake_case, camelCase, and kebab-case in a single identifier and you’ve effectively implemented chaos engineering at the lexical layer - production will self-destruct so you don’t have to schedule the game day
This is the same variable naming convention the contractor used before they "successfully migrated" our monolith to microservices and disappeared with half the budget
Even Satan has a style guide. Mixing snake, kebab, and camel case in one identifier isn't a convention violation - it's a war crime the linter refuses to autofix
The real hell isn't the mixed casing style - it's realizing this would actually compile in some languages, pass through code review because everyone's too horrified to comment, and eventually become 'legacy code we can't touch' that gets cargo-culted across the entire codebase for the next decade
Our polyglot stack tolerates snake_case, camelCase, and SCREAMING_SNAKE_CASE, but here_lOOk-At_it triggered a sev-hell bikeshed until a pre-commit linter exorcised the Studly-kebab-snake
Even Satan knows: inconsistent casing turns grep into an exorcism
Polyglot casing: camelCase to the client, snake_case in Postgres, kebab-case in URLs, and SCREAMING_SNAKE_CASE in env vars - incident severity is proportional to who forgets the mapper