5 exercises — ordering multiple adjectives correctly before technical nouns in design docs and code reviews.
Key patterns:
opinion → age → type/origin → noun — the general adjective-stacking order
size → qualifier → proper noun → noun — for phrases naming a specific product/technology
ambiguous, badly named — comma-separate co-equal opinion adjectives
The most specific classifying adjective sits closest to the noun
0 / 5 completed
1 / 5
Which noun phrase follows standard English adjective order for a design document?
English adjective order generally follows the sequence opinion → age/newness → origin/type/purpose before the noun. Here, robust is an opinion/quality adjective, new expresses age, and distributed classifies the type of caching layer, giving the natural order a new robust distributed caching layer. Native speakers judge other orderings as subtly "off" even though every version is technically parsable — this is why adjective order matters for professional-sounding technical writing.
2 / 5
Choose the correctly ordered noun phrase describing a database in an architecture diagram:
The conventional order is size → qualifier/origin-type → proper noun/brand before the head noun: large (size) precedes managed (a classifying qualifier describing the service model), which precedes the proper noun PostgreSQL, which precedes the head noun cluster. Reordering these — as in options A, C, and D — sounds unnatural to native readers even though the meaning is technically recoverable.
3 / 5
A code review comment describes a variable as: "This is _____ variable that should be renamed for clarity." Which ordering is correct?
When multiple opinion adjectives of similar rank modify the same noun (here, ambiguous and badly named, both evaluative), they are typically joined with a comma, with the more general or more important quality often placed first: an ambiguous, badly named global [variable]. This differs from cases mixing objective categories (size, age, origin) and opinions, where no comma is used and a strict order applies.
4 / 5
Which sentence uses correct adjective order for describing an API in documentation?
The standard order here follows age → opinion/quality → access-type → origin/type: new (age), lightweight (opinion/quality), public (classifying the access model), RESTful (classifying the architectural style) — closest to the noun since it most specifically categorizes the API. This produces a new lightweight public RESTful API, which reads naturally, unlike the scrambled orders in the other options.
5 / 5
In the phrase "a legacy monolithic Java application," why does "legacy" precede "monolithic," which precedes "Java"?
English stacks adjectives in a roughly fixed order of age/status → type/architecture → most specific classifier nearest the noun. Legacy describes the system's age/status, monolithic describes its architectural type, and Java most narrowly classifies what kind of application it is, so it sits immediately before the head noun. This is not alphabetical and not arbitrary — native speakers reliably judge scrambled versions as ungrammatical-sounding, which matters for polished technical documentation.