5 exercises — advanced connectors for design documents, incident reports, and code reviews: contrasts, conditions, consequences, and concessions.
Advanced connector cheat sheet
Contrast: whereas, while (contrastive), by contrast, on the other hand
Condition: provided that, as long as, given that, assuming that
Consequence: therefore, as a result, consequently, hence, thus
Concession: although, even though, albeit, despite, admittedly, granted that
Limitation: notwithstanding, in spite of, regardless of
0 / 5 completed
1 / 5
A design document compares two database strategies. Which sentence uses advanced linking words most effectively to present a contrast?
"Whereas" expresses a direct, simultaneous contrast — ideal for comparing architectural options.
Whereas (also: while in contrastive sense) introduces a subordinate clause that directly contrasts with the main clause. Both clauses are of equal weight and describe parallel situations.
Key contrast connectors and their nuances: • whereas / while: direct parallel contrast — "A scales vertically, whereas B scales horizontally." • however: introduces a qualification or exception — "Option A is well understood. However, it does not support flexible schemas." • by contrast: highlights a sharp difference (after a full stop) — "Option A is transactional. By contrast, Option B is eventually consistent." • on the other hand: introduces a second perspective — "Option A is simpler to operate. On the other hand, Option B offers better write throughput." • although / even though: contrast within one sentence, but with a concession — "Although Option A has higher operational overhead, it provides stronger consistency guarantees."
Option A uses "but" — correct but weak for technical documentation. Option B (semicolon only) implies contrast but lacks an explicit connector. Option D uses "however" correctly but is two separate sentences when "whereas" would be more elegant.
2 / 5
Which sentence correctly uses "provided that" in a technical context?
"Provided that" introduces a precise condition that must be met — ideal for performance requirements and architectural constraints.
Provided that (= only if, on the condition that) is stronger and more formal than a simple "if". It emphasises that the stated condition is specifically required for the main clause to hold.
Conditional linking words and their precision level: • if: general condition (informal to formal) • provided that / providing that: specific required condition — "The system will meet SLA, provided that it is deployed in two availability zones." • as long as: continuous condition — "The cache will remain valid as long as the TTL has not expired." • assuming (that): assumption in design reasoning — "Assuming that read traffic is 90%, a read replica will significantly reduce load." • given that: treats something as already established — "Given that we are already using PostgreSQL, adding Timescale DB is a natural extension." • on condition that: formal contractual condition — rarely used in engineering docs
Option A is grammatically acceptable but too simple for a precise technical constraint. Option C is vague — "everything" is imprecise. Option D is a fragment — "provided that" must introduce a full conditional clause.
3 / 5
An incident report explains a cascade failure. Which sentence uses "as a result" / "consequently" / "therefore" most precisely?
Use cause-effect connectors selectively — not one per sentence in a chain. One or two connectors anchor the causal chain.
Option A makes the classic mistake of using a different connector for every step. Each sentence becomes mechanical and the writing feels like a list rather than an explanation.
Cause-effect connectors and their register: • therefore: logical conclusion — "The payload exceeds 10MB; therefore, the upload must be chunked." • as a result / as a consequence: outcome of a process — "The deploy failed; as a result, the rollback was triggered." • consequently: formal, systemic consequence — "The health check endpoint returned 500; consequently, the load balancer removed all instances." • hence: formal, concise — common in academic and specification writing • thus: formal, often introduces a summary conclusion • causing / leading to / resulting in: participial phrases — "…overloaded the database, causing connection timeouts."
Option C is too vague — "because of the cache" doesn't explain which cache behaviour caused the issue.
4 / 5
A technical proposal needs to add a caveat to an otherwise strong claim. Which uses "notwithstanding" or "albeit" correctly?
"Albeit" introduces a concessive subordinate clause — it concedes a limitation without negating the main claim.
Albeit (= even though, although — but more formal and concise) is used after a positive main clause to add a minor qualification. It always introduces a participial phrase or adjective, never a full subject + verb clause.
✓ "The solution performs well, albeit at higher cost." ✓ "The migration succeeded, albeit more slowly than planned." ✗ "Albeit the migration was slow, it succeeded." — "albeit" cannot start a sentence as a regular conjunction
"Notwithstanding" — usage: • Formal; means "in spite of" or "despite" • "Notwithstanding the budget constraints, the team delivered on time." (before the conceded point) • "The timeline was compressed; the project was delivered successfully, notwithstanding." (after the main clause, as an adverb)
Option A ("Notwithstanding, the solution is good") is incomplete — notwithstanding as an adverb at the start needs a preceding context. Option C is grammatically weak — needs "notwithstanding the fact that". Option D is incorrect — "albeit" cannot open a sentence the way "although" can.
5 / 5
A code review comment needs to acknowledge a good approach before suggesting improvement. Which uses concessive linking words most professionally?
"Although" introduces a concessive clause — it acknowledges a positive before pivoting to a suggestion. Essential for professional code review tone.
Concessive connectors are powerful in code reviews because they: 1. Acknowledge the author's work before criticising 2. Frame the suggestion as an improvement, not a correction 3. Maintain a professional, collaborative tone
Concessive connector guide: • although / even though: full subordinate clause — "Although the implementation is correct, a hash map would reduce lookup time from O(n) to O(1)." • while: concessive use (formal) — "While this approach works for small datasets, it may not scale beyond 10K records." • despite / in spite of: followed by noun/gerund — "Despite the added complexity, this approach ensures thread safety." • admittedly: acknowledges the opposition's point — "Admittedly, the simpler approach would work for the current scale." • granted (that): concedes a point before refuting — "Granted that the test coverage is high, there is still a missing edge case for null inputs."
Option A uses "but" — grammatically correct but lacks the nuance of a professional code review. Option C has a grammar error: "Even though is a good approach" — missing subject. Option D uses "however" correctly, but "though" at the end is redundant and informal.