"snake case" meaning in All languages combined

{
  "etymology_text": "Coined in 2004 by Ruby programmer Gavin Kistner, from its resemblance to the long body of a snake, and by analogy with other naming schemes based on lower- and upper-case letters.",
  "head_templates": [
    {
      "args": {
        "1": "-"
      },
      "expansion": "snake case (uncountable)",
      "name": "en-noun"
    }
  ],
  "lang": "English",
  "lang_code": "en",
  "pos": "noun",
  "senses": [
    {
      "categories": [
        {
          "kind": "other",
          "name": "English entries with incorrect language header",
          "parents": [
            "Entries with incorrect language header",
            "Entry maintenance"
          ],
          "source": "w"
        },
        {
          "kind": "other",
          "name": "Pages with 1 entry",
          "parents": [],
          "source": "w"
        },
        {
          "kind": "other",
          "name": "Pages with entries",
          "parents": [],
          "source": "w"
        },
        {
          "kind": "topical",
          "langcode": "en",
          "name": "Programming",
          "orig": "en:Programming",
          "parents": [
            "Computing",
            "Software engineering",
            "Technology",
            "Computer science",
            "Engineering",
            "Software",
            "All topics",
            "Sciences",
            "Applied sciences",
            "Media",
            "Fundamental",
            "Communication"
          ],
          "source": "w"
        },
        {
          "kind": "topical",
          "langcode": "en",
          "name": "Writing systems",
          "orig": "en:Writing systems",
          "parents": [
            "Writing",
            "Human behaviour",
            "Language",
            "Human",
            "Communication",
            "All topics",
            "Fundamental"
          ],
          "source": "w"
        }
      ],
      "coordinate_terms": [
        {
          "word": "CamelCase"
        },
        {
          "word": "kebab case"
        },
        {
          "word": "Pascal case"
        }
      ],
      "derived": [
        {
          "word": "screaming snake case"
        },
        {
          "word": "snake-cased"
        }
      ],
      "examples": [
        {
          "ref": "2018, Camille McCue, Sarah Guthals, Helping Kids with Coding For Dummies®, John Wiley & Sons, Inc., →ISBN, page 130:",
          "text": "Some evidence shows that coders are better able to read code (their code and code written by others) when using snake_case, not camelCase naming.",
          "type": "quote"
        },
        {
          "ref": "2020, Jeanne Boyarsky, Scott Selikoff, OCP Oracle Certified Professional Java SE 11 Programmer I: Study Guide, Exam 1Z0-815, John Wiley & Sons, Inc., →ISBN, page 49:",
          "text": "While both camelCase and snake_case are perfectly valid syntax in Java, the development community functions better when everyone adopts the same style convention.",
          "type": "quote"
        },
        {
          "ref": "2020, Titus Winters, Tom Manshreck, Hyrum Wright, Software Engineering at Google: Lessons Learned from Programming Over Time, O’Reilly Media, Inc., →ISBN:",
          "text": "We were incorporating third-party Python libraries for some of our projects, leading to a mix within our codebase of our own CamelCase format with the externally preferred snake_case style.",
          "type": "quote"
        }
      ],
      "glosses": [
        "The practice of writing identifiers using underscores to separate words."
      ],
      "id": "en-snake_case-en-noun-P0pI-z3t",
      "links": [
        [
          "programming",
          "programming#Noun"
        ],
        [
          "identifier",
          "identifier"
        ],
        [
          "underscore",
          "underscore"
        ]
      ],
      "raw_glosses": [
        "(programming) The practice of writing identifiers using underscores to separate words."
      ],
      "synonyms": [
        {
          "word": "snake_case"
        }
      ],
      "tags": [
        "uncountable"
      ],
      "topics": [
        "computing",
        "engineering",
        "mathematics",
        "natural-sciences",
        "physical-sciences",
        "programming",
        "sciences"
      ]
    }
  ],
  "word": "snake case"
}

{
  "coordinate_terms": [
    {
      "word": "CamelCase"
    },
    {
      "word": "kebab case"
    },
    {
      "word": "Pascal case"
    }
  ],
  "derived": [
    {
      "word": "screaming snake case"
    },
    {
      "word": "snake-cased"
    }
  ],
  "etymology_text": "Coined in 2004 by Ruby programmer Gavin Kistner, from its resemblance to the long body of a snake, and by analogy with other naming schemes based on lower- and upper-case letters.",
  "head_templates": [
    {
      "args": {
        "1": "-"
      },
      "expansion": "snake case (uncountable)",
      "name": "en-noun"
    }
  ],
  "lang": "English",
  "lang_code": "en",
  "pos": "noun",
  "senses": [
    {
      "categories": [
        "English entries with incorrect language header",
        "English lemmas",
        "English multiword terms",
        "English nouns",
        "English terms with quotations",
        "English uncountable nouns",
        "Pages with 1 entry",
        "Pages with entries",
        "en:Programming",
        "en:Writing systems"
      ],
      "examples": [
        {
          "ref": "2018, Camille McCue, Sarah Guthals, Helping Kids with Coding For Dummies®, John Wiley & Sons, Inc., →ISBN, page 130:",
          "text": "Some evidence shows that coders are better able to read code (their code and code written by others) when using snake_case, not camelCase naming.",
          "type": "quote"
        },
        {
          "ref": "2020, Jeanne Boyarsky, Scott Selikoff, OCP Oracle Certified Professional Java SE 11 Programmer I: Study Guide, Exam 1Z0-815, John Wiley & Sons, Inc., →ISBN, page 49:",
          "text": "While both camelCase and snake_case are perfectly valid syntax in Java, the development community functions better when everyone adopts the same style convention.",
          "type": "quote"
        },
        {
          "ref": "2020, Titus Winters, Tom Manshreck, Hyrum Wright, Software Engineering at Google: Lessons Learned from Programming Over Time, O’Reilly Media, Inc., →ISBN:",
          "text": "We were incorporating third-party Python libraries for some of our projects, leading to a mix within our codebase of our own CamelCase format with the externally preferred snake_case style.",
          "type": "quote"
        }
      ],
      "glosses": [
        "The practice of writing identifiers using underscores to separate words."
      ],
      "links": [
        [
          "programming",
          "programming#Noun"
        ],
        [
          "identifier",
          "identifier"
        ],
        [
          "underscore",
          "underscore"
        ]
      ],
      "raw_glosses": [
        "(programming) The practice of writing identifiers using underscores to separate words."
      ],
      "tags": [
        "uncountable"
      ],
      "topics": [
        "computing",
        "engineering",
        "mathematics",
        "natural-sciences",
        "physical-sciences",
        "programming",
        "sciences"
      ]
    }
  ],
  "synonyms": [
    {
      "word": "snake_case"
    }
  ],
  "word": "snake case"
}