/pärm/
noun — “a parameter, squeezed down until only its intent remains.”
Parm is a further-compressed form of param, itself shorthand for “parameter.” It represents the tendency in computing cultures—especially those shaped by tight typing constraints, dense interfaces, or institutional jargon—to reduce commonly used technical terms into shorter, more efficient spoken and written forms.
The term is most strongly associated with IBM environments, where it appears in both documentation shorthand and conversational usage among developers and system engineers. In written form, parm is relatively rare outside of IBM-centric ecosystems, but in spoken technical dialogue it surfaces more naturally, especially in fast-paced discussions where brevity matters more than formal correctness.
Outside IBM culture, however, hackers and systems programmers tend to prefer the term arg (short for “argument”), which serves a similar conceptual role but fits more naturally into the linguistic habits of UNIX and hacker communities. Over time, arg became the dominant shorthand in many programming circles, while parm remained more localized and institution-specific.
Conceptually, a parm is simply a value passed into a function, procedure, or system component to influence its behavior. It might represent configuration, input data, flags, thresholds, or contextual information. The abstraction is fundamental to programming: rather than hardcoding behavior, systems become flexible by accepting external values that modify execution.
In practice, parm might appear like:
// function with parameters ("parms")
function connect(host, port, timeout) {
// host = server address
// port = network endpoint
// timeout = connection limit
}
// example call
connect("example.com", 443, 5000);Linguistically, parm is part of a broader pattern of compression in computing jargon—similar to var, arg, and other shortened identifiers that emerge when speed of communication matters more than grammatical formality. These reductions often persist because they are efficient, memorable, and reinforced through repetition in technical environments.
There is also a subtle cultural distinction embedded in the term. Where “parameter” suggests formal structure and documentation, parm suggests working familiarity—something handled frequently enough that it no longer needs to be fully spelled out. It is language shaped by usage pressure: what gets said often becomes shorter simply because typing and speaking it repeatedly becomes costly.