Notation

Notation packs structure into a line of symbols. 2 + 3 * 4 denotes one value, and which value depends on rules the reader already holds: which operation binds tighter, which way to read a tie between equals, where a group starts and ends. Those rules are precedence, associativity, and grouping. Read them wrong and you compute a different expression than the one the author wrote.

Notation carries meaning only when the writer and the reader share the same rules. Write the structure into brackets and it travels intact, because the grouping sits on the page. Leave it implicit, leaning on a convention the reader is assumed to know, and the expression is only as reliable as that shared assumption. This cluster works through where the assumption holds, where it breaks, and how explicit grouping turns a fragile expression into a robust one.

The pages in this cluster

• PEMDAS. The order arithmetic operations apply, why multiplication and division sit on one tier rather than two, and how the same precedence questions run through the operator tables of C, Java, Python, JavaScript, and Rust. The lesson that generalizes: a precedence table you do not actively remember is one to replace with brackets.

More pages join as the cluster grows, across operator precedence and associativity as a general subject, the notation of growth rates, and the trade between a dense symbolic form and explicit grouping.