An architect writes in an ADR: "We chose PostgreSQL because it is _____ and has strong support for ACID transactions." Which adjective best describes a system that can handle growth and increased load?
Scalable is correct. A scalable system can handle increased workload by adding resources (horizontally or vertically) without redesign. It is one of the core architectural qualities in system design. Ergonomic refers to ease of use and developer experience. Idiomatic means conforming to the natural conventions of a language or framework. Opinionated describes a tool that enforces specific conventions and constrains developer choices.
2 / 19
A senior developer comments in a code review: "This is not very _____ code — future developers will struggle to understand and modify it." Which adjective describes code that is easy to understand and change?
Maintainable is correct. Maintainability refers to how easy it is to read, understand, debug, and modify code over time. It is distinct from correctness (the code works) and performance (the code is fast). A common code review concern is that clever or dense code trades maintainability for brevity. Robust means resilient to errors and edge cases. Scalable refers to handling increased load. Reliable means consistently producing correct results.
3 / 19
A developer says in a code review: "This API design is more _____ than the previous version — it follows the conventions of the framework and feels natural to use." Which adjective describes code that follows the natural conventions of a language or framework?
Idiomatic is correct. Idiomatic code follows the natural patterns, idioms, and conventions of the programming language or framework. "Idiomatic Python" uses list comprehensions, context managers, and decorators the way the language intends. Idiomatic code is recognisable by experienced developers and integrates naturally with the ecosystem. Ergonomic refers to developer experience and ease of use. Opinionated means the tool enforces specific patterns. Robust means error-resilient.
4 / 19
A lead engineer describes a testing library: "The API is very _____ — it makes the common cases easy and guides you towards best practices." Which adjective describes a tool that is designed with the user's workflow in mind?
Ergonomic is correct. An ergonomic API or tool is designed to minimise friction, reduce cognitive load, and make the developer's job easier. It prioritises developer experience (DX). The term borrows from physical ergonomics (designing tools that fit the human body) and applies it to software. Opinionated means the tool enforces specific patterns. Scalable refers to load handling. Idiomatic refers to following language conventions.
5 / 19
A tech lead describes a framework in an RFC: "We chose Next.js because it is _____ — it makes clear decisions about routing, rendering, and project structure, so we don't have to." Which adjective describes a tool that enforces specific conventions?
Opinionated is correct. An opinionated framework or tool makes strong architectural decisions and constrains the user to follow them — reducing the "paradox of choice" but limiting flexibility. The opposite is "unopinionated" or "flexible". Ruby on Rails and Next.js are classic examples of opinionated frameworks. Robust means error-resilient. Reliable means consistently producing correct results. Idiomatic means following natural conventions of the language.
6 / 19
An SRE writes in an incident postmortem: "The payment service was not sufficiently _____ — a single node failure caused a complete outage." Which adjective describes a system that continues operating correctly despite failures?
Robust is correct. A robust system handles unexpected conditions, errors, and failures gracefully — it does not fail catastrophically when a single component fails. Robustness implies resilience and fault tolerance. Scalable refers to handling increased load. Maintainable refers to ease of modification. Ergonomic refers to developer experience.
7 / 19
A QA engineer writes in a test report: "The API is highly _____ — it consistently returns the correct response under all tested conditions, including edge cases." Which adjective describes a system that consistently produces correct results?
Reliable is correct. A reliable system consistently produces the correct result and behaves predictably. It is distinct from robust (which focuses on failure handling) — a reliable system simply does what it is supposed to do, consistently. In testing and SLA contexts, reliability is typically measured as uptime percentage or error rate. Idiomatic, opinionated, and ergonomic do not describe correctness or consistency.
8 / 19
Which sentence uses an evaluative adjective incorrectly?
Option D is incorrect. "Ergonomic" refers to developer experience and ease of use — it describes the human-computer interaction, not performance capacity. Handling 50,000 requests per second is a performance or scalability quality, not an ergonomic one. The correct adjective would be "performant", "high-throughput", or simply "fast". Options A, B, and C all use evaluative adjectives correctly.
9 / 19
A developer compares two ORM libraries: "Library A is more _____ but less _____ — it generates efficient SQL automatically but requires you to follow its specific patterns." Which pair of adjectives best completes this comparison?
Ergonomic / flexible is correct. The sentence describes a tool that is easy to use (ergonomic — generates SQL automatically) but constrains the developer (less flexible — requires specific patterns). This is a classic trade-off in framework design. "More ergonomic but less flexible" captures the trade-off precisely. Robust / scalable are about resilience and load handling — not the comparison being made. Idiomatic / maintainable do not describe the constraints and ease-of-use trade-off. Reliable / opinionated reverses the implied trade-off.
10 / 19
An architect presents three design qualities in order of priority: "For this system, _____ is more important than _____, which in turn is more important than _____." Which ordering reflects a typical distributed systems priority hierarchy for an e-commerce platform?
Reliable > scalable > maintainable reflects a common distributed systems priority hierarchy for an e-commerce platform. Reliability (uptime, correctness) is paramount — users must be able to complete purchases. Scalability enables handling peak traffic (e.g., Black Friday). Maintainability is important but secondary to the system being up and fast. This is the classic CAP theorem framing applied to e-commerce. Ergonomic, idiomatic, and opinionated are developer-experience qualities, not operational system qualities, so Options A and C are not appropriate here.
11 / 19
Reviewer: "This function is remarkably verbose. We could have achieved the same result with significantly less code."
The reviewer is using 'verbose' to describe code that's unnecessarily long and complicated. The key here is understanding that an evaluative adjective like *readable* directly assesses how easy something is to understand. Options A, B, and C represent other meanings of 'verbose,' failing to capture the intended critique.
12 / 19
Tech Lead: "We've adopted this new UI library. It's remarkably intuitive— developers are picking it up quickly without extensive training."
The tech lead is using 'intuitive' to describe the UI library's ease of use. 'User-friendly' is the most accurate evaluative adjective in this context, directly assessing how easy it is for users (developers) to understand and utilize. Options A, B and C represent different attributes that might be true of a library.
13 / 19
Reviewer: "This function is remarkably verbose. We could have achieved the same result with significantly less code."
The reviewer is using 'verbose' to describe code that's unnecessarily long and complicated. The key here is understanding that an evaluative adjective like *readable* directly assesses how easy something is to understand. Options A, B, and C represent other meanings of 'verbose,' failing to capture the intended critique.
14 / 19
Tech Lead: "We've adopted this new UI library. It's remarkably intuitive— developers are picking it up quickly without extensive training."
The tech lead is using 'intuitive' to describe the UI library's ease of use. 'User-friendly' is the most accurate evaluative adjective in this context, directly assessing how easy it is for users (developers) to understand and utilize. Options A, B and C represent different attributes that might be true of a library.
15 / 19
A junior developer writes in a Slack message: "The new caching layer is surprisingly efficient – it dramatically reduces database load and improves response times.". Which adjective best describes the performance of this caching layer?
The developer uses 'surprisingly efficient' to highlight a positive performance outcome. Option A correctly captures this meaning using the evaluative adjective 'remarkable'. Options B, C, and D all describe negative or neutral attributes, failing to reflect the intended praise.
16 / 19
A product manager writes in a requirements document: "The new service will be remarkably scalable – it can handle exponential increases in user traffic without performance degradation." Which adjective best describes the service's capability?
The product manager uses 'remarkably scalable' to emphasize the service's ability to handle significant growth. 'Robust' is the most appropriate evaluative adjective for a system designed to withstand high loads and maintain performance. Options A, B, and C all describe negative or neutral characteristics.
17 / 19
A QA engineer writes a bug report: "The API response is unexpectedly vague — it doesn't provide enough information for developers to troubleshoot effectively.". Which adjective best describes the API response in this context?
This question tests understanding of evaluative adjectives used to describe technical documentation. 'Unclear' accurately reflects the vague nature of the response, as opposed to 'verbose' (too much information), 'precise' (accurate and specific), or 'detailed' (providing a lot of detail). The focus is on clarity for troubleshooting.
18 / 19
A QA engineer writes a bug report: "The API response is unexpectedly vague — it doesn't provide enough information for developers to troubleshoot effectively.". Which adjective best describes the API response in this context?
This question tests understanding of evaluative adjectives used to describe technical documentation. 'Unclear' accurately reflects the vague nature of the response, as opposed to 'verbose' (too much information), 'precise' (accurate and specific), or 'detailed' (providing a lot of detail). The focus is on clarity for troubleshooting.
19 / 19
A QA engineer writes a bug report: "The API response is unexpectedly vague — it doesn't provide enough information for developers to troubleshoot effectively.". Which adjective best describes the API response in this context?
This question tests understanding of evaluative adjectives used to describe technical documentation. 'Unclear' accurately reflects the vague nature of the response, as opposed to 'verbose' (too much information), 'precise' (accurate and specific), or 'detailed' (providing a lot of detail). The focus is on clarity for troubleshooting.
What will I practise in "Evaluative Adjectives in Technical Writing — Grammar Exercise"?
Practice using robust, scalable, reliable, maintainable, idiomatic, ergonomic, opinionated correctly in technical architecture reviews and documentation.
How many exercises are in this module?
This module has 19 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.