Programming Case Styles

snake_case Pros: Concise when it consists of a few words. Cons: Redundant as hell when it gets longer. push_something_to_first_queue, pop_what, get_whatever... PascalCase Pros: Seems neat. GetItem, SetItem, Convert, ... Cons: Barely used. (Why?) camelCase Pros: Widely used in the programmer community. Cons: Looks ugly when a few methods are m-worded. push, reserve, beginBuilding, ... skewer-case Pros: Easy to type. easier-than-underscore,... Cons: Any sane language freaks out when you try it. SCREAMING_SNAKE_CASE Pros: Can demonstrate your anger with text. Cons: Makes your eyes dead. LOOK_AT_THIS, LOOK_AT_THAT, LOOK_HERE_YOU_MORON, ... nocase Pros: Looks professional. Cons: Misleading af. supersexyhippopotamus, bool penisbig, ... fUcKtHeCaSe Pros: Can live outside of the law. Cons: Can be out of a job.

The meme compares programming naming conventions using cartoon animals and increasingly chaotic examples. Snake case is concise but becomes redundant, PascalCase looks neat but is rarely used, camelCase is common but can look ugly, and the joke escalates through skewer-case, screaming snake case, no case, and random capitalization. It is sent as a humorous reaction to debates about coding style and naming conventions. EN: The meme compares programming naming conventions using cartoon animals and increasingly chaotic examples. Snake case is concise but becomes redundant, PascalCase looks neat but is rarely used, camelCase is common but can look ugly, and the joke escalates through skewer-case, screaming snake case, no case, and random capitalization. It is sent as a humorous reaction to debates about coding style and naming conventions.

• @ithueti / 1123 2019-07-29
• @profunctor_io / 2748 2019-07-29