5 exercises — choosing the right concessive form (although/while/whereas/even though/despite/however) when discussing technical trade-offs in ADRs, RFCs, blog posts, and code reviews.
0 / 5 completed
1 / 5
An architecture decision record (ADR) states: "_____ GraphQL provides greater query flexibility, it introduces additional complexity at the gateway layer." Which concessive is most appropriate?
Option B is correct."Although" is the standard concessive subordinator for acknowledging a positive quality while introducing a counterpoint: "Although GraphQL provides flexibility, it introduces complexity." This structure is ideal for ADRs, which must document trade-offs. "Whereas" (option D) contrasts two different subjects ("REST is simple, whereas GraphQL is flexible") — not the same structure. "Because" expresses reason; "therefore" expresses consequence. Use "although/even though/while" for within-subject concessions in technical trade-off discussions.
2 / 5
A technical blog post compares two deployment strategies: "Blue-green deployment eliminates downtime. _____, it requires double the infrastructure during transition." Which concessive adverbial is correct as a sentence connector?
Option C is correct."However" is a concessive adverbial connector — it connects two separate sentences, introducing a counterpoint to the previous sentence. "Although" and "despite" are subordinating/prepositional concessives — they must be used within a single sentence. "However" at the start of a new sentence is the natural choice when the concession follows a full stop. "Whereas" is for contrast between parallel subjects, not for a simple trade-off counterpoint. Connector: However / Nevertheless / That said. Subordinator: Although / Even though / While.
3 / 5
A capacity planning report states: "_____ the increased cache hit rate, overall system latency has not improved measurably." Which concessive preposition is correct?
Option C is correct."Despite + noun phrase" is the correct structure when the concessive is introduced by a noun phrase ("the increased cache hit rate") rather than a clause. "Although" and "even though" and "while" are subordinating conjunctions — they require a subject and verb: "Although the cache hit rate increased…" "Despite" (and "in spite of") take a noun phrase or gerund: "Despite the increase / Despite improving the cache hit rate…". This is a common error in technical writing — confusing prepositional and conjunctional concessives.
4 / 5
A code review comment reads: "This approach works, _____ it relies on implementation details that may change in future versions of the library." Which concessive is most appropriate for mid-sentence use?
Option A is correct."Although" is correct when used as a subordinating conjunction within a sentence after a comma: "This approach works, although it relies on implementation details…". This is a legitimate mid-sentence position for "although." "Despite" and "in spite of" (options B and D) require a noun phrase, not a full clause ("it relies on…" is a clause, not a noun phrase). "However" (option C) is a sentence connector — placing it after a comma ("works, however it relies on…") is incorrect without a semicolon or period before it.
5 / 5
Which sentence most effectively uses a concessive to present a technical trade-off in an RFC?
Option B is correct."Whereas" is ideal for RFCs and ADRs when contrasting two properties of the same subject: "Whereas X provides benefit, it also introduces risk." The sentence clearly articulates both the advantage (latency) and the trade-off (stale reads). Option A presents the trade-off as two unconnected statements. Option C is vague and circular. Option D ("Despite latency benefits") is grammatically acceptable but too vague — "is bad for some use cases" lacks the precision expected in RFCs. For formal trade-off documentation, use "whereas/while/although" with precise technical claims on both sides.