Why Using Pinyin for Variable Names Is Discouraged in Programming

On Zhihu a popular question asks why programming advice often warns against using pinyin for naming.

An amusing answer shows a sentence composed entirely of "shi", highlighting the difficulty of expression.

Using pinyin for naming is likened to trying to play soccer with a basketball – it simply doesn’t fit.

Programming requires adherence to widely accepted code conventions, which are distilled from professional standards.

Ignoring the well‑paved path of prior practice leads to problems.

Pinyin naming exemplifies a breach of coding norms and has several disadvantages:

1. Poor readability

Code is read by others, not just the author. Pinyin is a phonetic tool, not a language, leading to ambiguity, multiple meanings, and limited to mainland China, making it incomprehensible to most global developers.

2. Inconvenient

Although pinyin may feel natural, it clashes with English‑based language keywords and syntax, making it hard to convey intent. For example, a Python function to create a list should be named create_list , not the pinyin chaungjianliebiao .

3. Non‑standard

While technically possible, pinyin naming is considered unprofessional and hinders personal technical growth, similar to using the wrong ball for a sport.

Finally, the article shares Python PEP naming conventions:

Variables, functions, and attributes should be lowercase with underscores for multiple words.

Protected instance attributes start with a single underscore.

Private instance attributes start with double underscores.

Class and exception names use capitalized words (CamelCase).

Module‑level constants are uppercase with underscores.

The first parameter of instance methods should be named self .

The first parameter of class methods should be named cls .