Whatever the language community and the team I'm in do. Anything that goes strongly against the grain is you choosing to be hard to work with. Especially when t

Whatever the language community and the team I'm in do. Anything that goes strongly against the grain is you choosing to be hard to work with. Especially when there's already a convention in place. A variable like this in C would communicate that the value is meant to be a constant (maybe is a constant via a macro definition): int CONTACT_ID = 10; // weird if it's meant to be reassigned later // elsewhere int x = CONTACT_ID; If I saw this after the initial definition: CONTACT_ID = 20; I'd be very confused as to why they chose to shout the name when that, by convention, marks it as a constant but are now assigning to it. Choose to communicate poorly at your own peril. Naming conventions (including these typographical elements like capitalization and case style) are how you communicate with other people.