Which case goes where
The conventions are arbitrary but strongly held, and following them is the difference between code that reads as native and code that reads as translated. JavaScript and Java use camelCase for variables and PascalCase for types; Python and Ruby use snake_case; CSS classes and URL paths use kebab-case; environment variables and constants use CONSTANT_CASE.
The friction shows up at boundaries. A Python API returning snake_case JSON consumed by a TypeScript client that expects camelCase forces a decision: convert at the edge, or accept mixed conventions throughout. Converting at the edge is almost always right, and doing it in one place is what keeps it from being done inconsistently in twenty.