5 exercises — practise forming and using compound nouns that are essential vocabulary in software engineering: word order, singular modifiers, hyphens, and noun vs adjective forms.
Compound nouns: key rules
Modifier first, head last:deployment pipeline, not pipeline deployment
Modifier stays singular:test automation, not tests automation
No apostrophe:error handling, not error's handling
Noun vs adjective:type safety (noun) vs type-safe (adjective)
0 / 5 completed
1 / 5
A job description reads: "Experience with ___ is required." The blank should refer to the practice of managing the process of deploying software automatically. Which compound noun is correct?
Deployment pipeline is correct. In English compound nouns, the modifier comes first and the head noun (the main thing) comes last: deployment (modifier) + pipeline (head) = a pipeline for deployments. This is the standard order for most technical compound nouns: the first noun describes the type or purpose; the second is the thing itself. Common examples: deployment pipeline, error handling, release cycle, feature flag, load balancer, connection pool. Option A (pipeline deployment) would mean "the deployment of a pipeline" — a different, niche meaning. Option C uses a gerund — incorrect in this compound structure. Option D uses a prepositional phrase — grammatically possible but non-standard in technical English; compounds are preferred.
2 / 5
A code review comment reads: "We need proper ___ to prevent unexpected exceptions from propagating." Which compound noun is correct for the practice of dealing with errors?
Error handling is correct. This is a classic noun + gerund compound — extremely common in software terminology: error handling, exception handling, event logging, load balancing, memory caching. Structure: error (noun, modifier) + handling (gerund, acting as head noun). Note: in these compounds, the gerund functions as a noun, not a verb. The plural of the modifier noun is not used: error handling, not errors handling (even when handling multiple errors). The first noun in a compound modifier does not take a possessive: error's handling is non-standard in technical English. This pattern is one of the most productive in software vocabulary: memory management, state management, rate limiting, dependency injection.
3 / 5
A TypeScript documentation page is titled: "Ensuring ___ in your codebase." The blank refers to the property of having correct, well-defined types. Which compound noun is standard?
Type safety is correct. Type safety follows the standard noun + noun compound pattern: type (modifier) + safety (head). As a noun phrase, it refers to the property of a system. Note the distinction between: type safety (noun — "ensure type safety") and type-safe (compound adjective — "a type-safe codebase"). Both are correct in their roles. In technical writing, compound nouns like this are never hyphenated when used as a standalone noun: type safety, null safety, thread safety, memory safety. They are hyphenated only when used as pre-nominal modifiers: a type-safe language, a memory-safe system. Option A reverses the order. Option B pluralises the modifier — non-standard. Option C is an adjective form, not a noun phrase.
4 / 5
A DevOps engineer writes: "Set up the ___ to auto-scale based on CPU usage." The blank refers to the automated management of server resources. Which is the correct compound noun?
Infrastructure management is correct. Noun + noun compounds are standard in DevOps and cloud vocabulary: infrastructure management, resource provisioning, cluster autoscaling, capacity planning. The compound noun is preferred over the prepositional phrase (option C: management of infrastructure) in technical writing because it is more concise and idiomatic. Both are grammatically valid, but the compound noun sounds more natural to native speakers of technical English and is dominant in documentation. Option B (infrastructure managing) is incorrect — managing as a gerund can function as a noun, but the compound requires the gerund (management) as the head: infrastructure management. Gerunds as second elements in compounds are used differently: load balancing, event sourcing — here they describe an activity.
5 / 5
Which of the following lists contains only correctly formed and standard technical compound nouns?
Option D — codebase quality, test automation, build pipeline, structured logging — contains all correctly formed standard technical compound nouns. Analysis: codebase quality (noun + noun, head last ✓); test automation (noun + noun, not "tests automation" — modifier stays singular ✓); build pipeline (noun + noun ✓); structured logging (adjective + gerund-noun — a standard pattern ✓). Option A has errors: tests automation (plural modifier — non-standard), pipelines build (reversed order), logging structured (reversed order). Option B: quality codebase (reversed — means "a codebase of quality", not a natural compound), automated testing is actually valid. Option C: code base quality (codebase is one word), pipeline build (reversed order). Key rule: modifier first, head last; modifier singular; no apostrophe.