10 exercises — bracketing best-case and worst-case outcomes with "at best" and "at worst" in estimates, risk assessments, and trade-off summaries, including comma placement and common misuses.
Quick reference
At best: brackets a claim at its most optimistic possible limit
At worst: brackets a claim at its most pessimistic possible limit
Standard order: best-case first, then worst-case, when presenting a risk range
Don't confuse with at least / at most (numeric floor/ceiling, no good/bad connotation)
Comma rule: comma after when fronted; commas surrounding when mid-sentence
0 / 38 completed
1 / 38
A performance review comment reads: "This optimization saves 2ms per request ___ — it's not going to fix our latency problem." Which phrase correctly signals the upper limit of an optimistic estimate?
At best brackets a claim at its most optimistic outer limit — "this is the best-case outcome, and even that isn't good enough." "This optimization saves 2ms per request at best" means even under the most favorable conditions, the saving tops out at 2ms. "At last" means "finally" (unrelated). "At least" sets a minimum floor, not a ceiling — the opposite meaning ("saves 2ms at least" would mean 2ms or more, i.e., could be much better). "At length" means "in detail" or "eventually" — unrelated.
2 / 38
Which sentence correctly uses "at worst" to bracket the most pessimistic possible outcome?
"The migration will take two hours, at worst" means: even in the worst-case scenario, it will not exceed two hours — this is the pessimistic ceiling. "At last" (finally) and "at all costs" (regardless of cost/sacrifice) are unrelated fixed phrases. "At least" would flip the meaning to a minimum floor: "it will take two hours at least" implies it could take longer, which is the opposite framing from "at worst."
3 / 38
A risk assessment states: "If the vendor API goes down, ___ we fall back to cached data; ___ we lose real-time pricing entirely." Which pair correctly brackets the best-case and worst-case outcomes?
"If the vendor API goes down, at best we fall back to cached data; at worst we lose real-time pricing entirely." The standard order brackets the outcome range from most favorable to least favorable: at best (the good outcome within a bad situation) → at worst (the truly bad outcome). Reversing the order (option B) is possible but less natural rhetorically — native usage strongly favors best-then-worst when presenting a risk range. "At least / at most" (option C) describes quantities (minimum/maximum amounts), not qualitative best/worst outcomes. "In theory / in practice" (option D) is a different contrast entirely (design vs. reality, not favorable vs. unfavorable outcome).
4 / 38
Which sentence shows "at best" used to deliver a backhanded or lukewarm evaluation, common in blunt code review feedback?
"This solution is functional at best — it works, but the code is unreadable and untested" uses "at best" idiomatically to deliver a damning-with-faint-praise evaluation: the most positive thing that can honestly be said is a modest claim ("functional"), implying everything else about it falls short. This is a very common rhetorical pattern in blunt but professional code review feedback. Option A ("elegant at best") uses a strongly positive adjective, which contradicts the deflating tone "at best" is meant to create — "elegant" is not a modest, minimal claim. Option C garbles the structure by trying to attach "at best" to two adjectives ambiguously. Option D redundantly repeats "at best" twice in the same short sentence, which is unnatural.
5 / 38
Which sentence correctly places "at best" at the START of a sentence rather than at the end?
"At best, the feature flag rollback buys us an hour to investigate." Fronting "at best" (or "at worst") at the start of a sentence requires a comma immediately after it, before the main clause, exactly like other adverbial disjuncts ("However, ..." / "In principle, ..."). "At best" is a fixed two-word phrase with no article — "at the best" (option B) incorrectly inserts "the." Options C and D scramble the word order of the fixed phrase itself, which is never grammatical.
6 / 38
Which explanation of "at best" / "at worst" as SCALAR markers (vs. simple adjectives) is correct?
"At best" and "at worst" function as scalar bracketing markers: they name one extreme of a range (the most favorable or least favorable point) while implicitly acknowledging the true outcome could fall anywhere along that scale, not stating a single certain fact. This works for both numeric claims ("saves 2ms at best") and qualitative claims ("functional at best"). They are unrelated to "always/never" (which are about frequency, not degree), and they are not restricted to negative sentences — "at best" often appears in cautiously positive framing too ("At best, this refactor cuts build time in half").
7 / 38
Which sentence misuses "at worst" by attaching it to a claim that has no scale of severity at all?
"At worst, the file is named 'config.json'" is meaningless — a filename is a fixed fact with no severity scale; there is no "better or worse" version of what a file is named, so "at worst" adds nothing and sounds like a non-sequitur. The other three sentences correctly attach "at worst" to genuine risk scenarios where outcomes range from mild (short outage, minor data loss) to severe (a failed rollback requiring manual intervention) — exactly the kind of claim this scalar marker is designed for.
8 / 38
A staff engineer hedges an estimate in a planning meeting: "Realistically, this will take three days ___ , maybe a week ___ if we hit unexpected schema issues." Which pair correctly completes the sentence?
"...this will take three days at best, maybe a week at worst if we hit unexpected schema issues" — three days is the optimistic floor of effort (the best case), a week is the pessimistic ceiling (the worst case) if complications arise. "At least / at most" (option B) describes numeric minimum/maximum amounts without the connotation of good/bad outcome — grammatically plausible but loses the qualitative best/worst framing the sentence is going for. "In principle / in practice" (option C) contrasts theory with reality, a different logical relationship. "So far / so to speak" (option D) are unrelated discourse markers.
9 / 38
Which sentence correctly uses "if at best" — a related but distinct hedge questioning whether even the best case is achievable — versus plain "at best"?
Both are grammatical and closely related: "at best" states the outer limit of a favorable estimate directly. "if at best" adds a layer of doubt about whether even that limit will be reached, often implying skepticism about the estimate itself — a subtle nuance more common in spoken or informal written hedging. In this sentence, both readings work: the reduction "at best" reaches 10%, and given the noisy metric, that itself might be optimistic ("if at best"). Neither is ungrammatical, and no meaningful difference blocks either from being used here.
10 / 38
Which sentence correctly combines "at best" and "at worst" in a single balanced trade-off summary for a design doc?
"The caching layer reduces P99 latency by 40% at best and, at worst, adds a stale-data window of up to 60 seconds" correctly pairs each bracket with its matching outcome: the latency reduction is the positive/best-case benefit, and the stale-data window is the negative/worst-case cost. Option B swaps the brackets onto the wrong outcomes (illogically calling the latency reduction the "worst" case). Options C and D fuse "at best" and "at worst" into one ungrammatical unit ("at best at worst" / "at best worst"), which is never a valid construction — the two phrases must remain separate and each attach to its own clause or outcome.
11 / 38
PR Description: "Initial implementation of the new user authentication flow. At best, this will reduce login latency by 50ms; at worst, it might introduce a new bottleneck."
The phrase "at best/worst" here functions as scalar markers, indicating a range of possible outcomes rather than simple adjectives describing the implementation. The correct option accurately reflects this – it recognizes that there's a realistic chance of both improvement and problems. Incorrect options incorrectly interpret 'at worst' as a purely negative descriptor or assume an overly confident prediction; often developers use these phrases to temper expectations in a technical discussion.
12 / 38
Sarah: "The new API endpoint returns data in JSON format. At best, it'll provide us with a clean and consistent dataset; at worst, the response might be malformed and require significant parsing."
During a code review discussion about integrating this API, Mark asks:
Which phrase most accurately captures Sarah's assessment of potential risks regarding the API endpoint?
Sarah uses "at best" and "at worst" to express a balanced view of potential outcomes. This isn't simply describing positive or negative attributes—it's signaling a recognition of *scale*. The phrase correctly identifies that she's acknowledging both an optimistic and pessimistic scenario related to the API's behavior, prompting further investigation and planning for contingencies. Option A is overly confident, option C is dismissive, and option D incorrectly assumes guaranteed performance.
13 / 38
PR Description: "Initial implementation of the new user authentication flow. At best, this will reduce login latency by 50ms; at worst, it might introduce a new bottleneck."
The phrase "at best/worst" here functions as scalar markers, indicating a range of possible outcomes rather than simple adjectives describing the implementation. The correct option accurately reflects this – it recognizes that there's a realistic chance of both improvement and problems. Incorrect options incorrectly interpret 'at worst' as a purely negative descriptor or assume an overly confident prediction; often developers use these phrases to temper expectations in a technical discussion.
14 / 38
Sarah: "The new API endpoint returns data in JSON format. At best, it'll provide us with a clean and consistent dataset; at worst, the response might be malformed and require significant parsing."
During a code review discussion about integrating this API, Mark asks:
Which phrase most accurately captures Sarah's assessment of potential risks regarding the API endpoint?
Sarah uses "at best" and "at worst" to express a balanced view of potential outcomes. This isn't simply describing positive or negative attributes—it's signaling a recognition of *scale*. The phrase correctly identifies that she's acknowledging both an optimistic and pessimistic scenario related to the API's behavior, prompting further investigation and planning for contingencies. Option A is overly confident, option C is dismissive, and option D incorrectly assumes guaranteed performance.
15 / 38
PR Description: "Initial implementation of the new user authentication flow. At best, this will reduce login latency by 50ms; at worst, it might introduce a new bottleneck."
The phrase "at best/worst" here functions as scalar markers, indicating a range of possible outcomes rather than simple adjectives describing the implementation. The correct option accurately reflects this – it recognizes that there's a realistic chance of both improvement and problems. Incorrect options incorrectly interpret 'at worst' as a purely negative descriptor or assume an overly confident prediction; often developers use these phrases to temper expectations in a technical discussion.
16 / 38
Sarah: "The new API endpoint returns data in JSON format. At best, it'll provide us with a clean and consistent dataset; at worst, the response might be malformed and require significant parsing."
During a code review discussion about integrating this API, Mark asks:
Which phrase most accurately captures Sarah's assessment of potential risks regarding the API endpoint?
Sarah uses "at best" and "at worst" to express a balanced view of potential outcomes. This isn't simply describing positive or negative attributes—it's signaling a recognition of *scale*. The phrase correctly identifies that she's acknowledging both an optimistic and pessimistic scenario related to the API's behavior, prompting further investigation and planning for contingencies. Option A is overly confident, option C is dismissive, and option D incorrectly assumes guaranteed performance.
17 / 38
PR Description: "Initial implementation of the new user authentication flow. At best, this will reduce login latency by 50ms; at worst, it might introduce a new bottleneck."
The phrase "at best/worst" here functions as scalar markers, indicating a range of possible outcomes rather than simple adjectives describing the implementation. The correct option accurately reflects this – it recognizes that there's a realistic chance of both improvement and problems. Incorrect options incorrectly interpret 'at worst' as a purely negative descriptor or assume an overly confident prediction; often developers use these phrases to temper expectations in a technical discussion.
18 / 38
Sarah: "The new API endpoint returns data in JSON format. At best, it'll provide us with a clean and consistent dataset; at worst, the response might be malformed and require significant parsing."
During a code review discussion about integrating this API, Mark asks:
Which phrase most accurately captures Sarah's assessment of potential risks regarding the API endpoint?
Sarah uses "at best" and "at worst" to express a balanced view of potential outcomes. This isn't simply describing positive or negative attributes—it's signaling a recognition of *scale*. The phrase correctly identifies that she's acknowledging both an optimistic and pessimistic scenario related to the API's behavior, prompting further investigation and planning for contingencies. Option A is overly confident, option C is dismissive, and option D incorrectly assumes guaranteed performance.
19 / 38
David: "This feature is… well, at worst, it's functional. At best, it might actually be useful."
Which option best describes David's tone and the intended use of 'at worst/at best' in this comment?
'At worst/at best' functions as scalar brackets here, indicating a range of possible results. David is using it to cautiously assess the feature, acknowledging potential downsides while leaving room for positive outcomes. The incorrect options misinterpret 'at worst' as just an adjective or fail to grasp the hedging intent.
20 / 38
Liam writes in a Slack channel: "I've refactored the database query. At worst, it'll be slower; at best, it'll be faster."
Which sentence demonstrates the correct placement of 'at worst/at best' to effectively convey a potential range of outcomes?
'At worst/at best' needs to follow the subject. Placing 'at worst' first creates a less natural flow and obscures the intended scalar bracket usage – it's more common to state the negative outcome before the positive one when describing potential impacts.
21 / 38
Maria is drafting a PR description: "The new caching layer implementation. At best, it reduces server load; at worst, it introduces unexpected latency."
Which of the following best describes Maria's use of 'at best' and 'at worst'?
Maria's sentence accurately demonstrates the core function of 'at best/at worst' – presenting a range of possible outcomes from a design decision. It's a balanced assessment highlighting both potential gains (reduced load) and losses (increased latency), utilizing scalar brackets to frame those possibilities.
22 / 38
Ben sends this message in a standup update: "I'm working on the new API integration. At worst, it will take two weeks; at best, I'll have it done in five days."
Which sentence demonstrates an inappropriate use of 'at worst/at best'?
'At worst/at best' indicates a *range* of possibilities. Ben's use implies a strict binary – either two weeks or five days – which contradicts the hedging intent of the phrase. It's a misapplication where 'at worst' simply acts as an adjective describing the time estimate.
23 / 38
Chloe writes in a code review comment: "This function is complex. At best, it's elegant; at worst, it's a nightmare to maintain."
Which of the following represents the MOST accurate interpretation of Chloe's feedback?
Chloe uses 'at best/at worst' to present a range of potential qualities – elegance versus difficulty. This is a standard way to frame feedback, acknowledging both positive and negative aspects while leaving room for interpretation and improvement. It's not just describing the code; it's evaluating its overall impact.
24 / 38
David: "This feature is… well, at worst, it's functional. At best, it might actually be useful."
Which option best describes David's tone and the intended use of 'at worst/at best' in this comment?
'At worst/at best' functions as scalar brackets here, indicating a range of possible results. David is using it to cautiously assess the feature, acknowledging potential downsides while leaving room for positive outcomes. The incorrect options misinterpret 'at worst' as just an adjective or fail to grasp the hedging intent.
25 / 38
Liam writes in a Slack channel: "I've refactored the database query. At worst, it'll be slower; at best, it'll be faster."
Which sentence demonstrates the correct placement of 'at worst/at best' to effectively convey a potential range of outcomes?
'At worst/at best' needs to follow the subject. Placing 'at worst' first creates a less natural flow and obscures the intended scalar bracket usage – it's more common to state the negative outcome before the positive one when describing potential impacts.
26 / 38
Maria is drafting a PR description: "The new caching layer implementation. At best, it reduces server load; at worst, it introduces unexpected latency."
Which of the following best describes Maria's use of 'at best' and 'at worst'?
Maria's sentence accurately demonstrates the core function of 'at best/at worst' – presenting a range of possible outcomes from a design decision. It's a balanced assessment highlighting both potential gains (reduced load) and losses (increased latency), utilizing scalar brackets to frame those possibilities.
27 / 38
Ben sends this message in a standup update: "I'm working on the new API integration. At worst, it will take two weeks; at best, I'll have it done in five days."
Which sentence demonstrates an inappropriate use of 'at worst/at best'?
'At worst/at best' indicates a *range* of possibilities. Ben's use implies a strict binary – either two weeks or five days – which contradicts the hedging intent of the phrase. It's a misapplication where 'at worst' simply acts as an adjective describing the time estimate.
28 / 38
Chloe writes in a code review comment: "This function is complex. At best, it's elegant; at worst, it's a nightmare to maintain."
Which of the following represents the MOST accurate interpretation of Chloe's feedback?
Chloe uses 'at best/at worst' to present a range of potential qualities – elegance versus difficulty. This is a standard way to frame feedback, acknowledging both positive and negative aspects while leaving room for interpretation and improvement. It's not just describing the code; it's evaluating its overall impact.
29 / 38
David: "This feature is… well, at worst, it's functional. At best, it might actually be useful."
Which option best describes David's tone and the intended use of 'at worst/at best' in this comment?
'At worst/at best' functions as scalar brackets here, indicating a range of possible results. David is using it to cautiously assess the feature, acknowledging potential downsides while leaving room for positive outcomes. The incorrect options misinterpret 'at worst' as just an adjective or fail to grasp the hedging intent.
30 / 38
Liam writes in a Slack channel: "I've refactored the database query. At worst, it'll be slower; at best, it'll be faster."
Which sentence demonstrates the correct placement of 'at worst/at best' to effectively convey a potential range of outcomes?
'At worst/at best' needs to follow the subject. Placing 'at worst' first creates a less natural flow and obscures the intended scalar bracket usage – it's more common to state the negative outcome before the positive one when describing potential impacts.
31 / 38
Maria is drafting a PR description: "The new caching layer implementation. At best, it reduces server load; at worst, it introduces unexpected latency."
Which of the following best describes Maria's use of 'at best' and 'at worst'?
Maria's sentence accurately demonstrates the core function of 'at best/at worst' – presenting a range of possible outcomes from a design decision. It's a balanced assessment highlighting both potential gains (reduced load) and losses (increased latency), utilizing scalar brackets to frame those possibilities.
32 / 38
Ben sends this message in a standup update: "I'm working on the new API integration. At worst, it will take two weeks; at best, I'll have it done in five days."
Which sentence demonstrates an inappropriate use of 'at worst/at best'?
'At worst/at best' indicates a *range* of possibilities. Ben's use implies a strict binary – either two weeks or five days – which contradicts the hedging intent of the phrase. It's a misapplication where 'at worst' simply acts as an adjective describing the time estimate.
33 / 38
Chloe writes in a code review comment: "This function is complex. At best, it's elegant; at worst, it's a nightmare to maintain."
Which of the following represents the MOST accurate interpretation of Chloe's feedback?
Chloe uses 'at best/at worst' to present a range of potential qualities – elegance versus difficulty. This is a standard way to frame feedback, acknowledging both positive and negative aspects while leaving room for interpretation and improvement. It's not just describing the code; it's evaluating its overall impact.
34 / 38
David: "This feature is… well, at worst, it's functional. At best, it might actually be useful."
Which option best describes David's tone and the intended use of 'at worst/at best' in this comment?
'At worst/at best' functions as scalar brackets here, indicating a range of possible results. David is using it to cautiously assess the feature, acknowledging potential downsides while leaving room for positive outcomes. The incorrect options misinterpret 'at worst' as just an adjective or fail to grasp the hedging intent.
35 / 38
Liam writes in a Slack channel: "I've refactored the database query. At worst, it'll be slower; at best, it'll be faster."
Which sentence demonstrates the correct placement of 'at worst/at best' to effectively convey a potential range of outcomes?
'At worst/at best' needs to follow the subject. Placing 'at worst' first creates a less natural flow and obscures the intended scalar bracket usage – it's more common to state the negative outcome before the positive one when describing potential impacts.
36 / 38
Maria is drafting a PR description: "The new caching layer implementation. At best, it reduces server load; at worst, it introduces unexpected latency."
Which of the following best describes Maria's use of 'at best' and 'at worst'?
Maria's sentence accurately demonstrates the core function of 'at best/at worst' – presenting a range of possible outcomes from a design decision. It's a balanced assessment highlighting both potential gains (reduced load) and losses (increased latency), utilizing scalar brackets to frame those possibilities.
37 / 38
Ben sends this message in a standup update: "I'm working on the new API integration. At worst, it will take two weeks; at best, I'll have it done in five days."
Which sentence demonstrates an inappropriate use of 'at worst/at best'?
'At worst/at best' indicates a *range* of possibilities. Ben's use implies a strict binary – either two weeks or five days – which contradicts the hedging intent of the phrase. It's a misapplication where 'at worst' simply acts as an adjective describing the time estimate.
38 / 38
Chloe writes in a code review comment: "This function is complex. At best, it's elegant; at worst, it's a nightmare to maintain."
Which of the following represents the MOST accurate interpretation of Chloe's feedback?
Chloe uses 'at best/at worst' to present a range of potential qualities – elegance versus difficulty. This is a standard way to frame feedback, acknowledging both positive and negative aspects while leaving room for interpretation and improvement. It's not just describing the code; it's evaluating its overall impact.
What will I practise in ""At Best" / "At Worst" as Scalar Brackets — IT English Grammar"?
Practice using "at best" and "at worst" to bracket optimistic and pessimistic outcomes in risk assessments, estimates, and code review feedback.
How many exercises are in this module?
This module has 38 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.