5 exercises — choosing between would, could, might, and should in design discussions, risk assessments, code reviews, and proposals.
0 / 23 completed
1 / 23
In a design discussion, an engineer says: "We _____ use Redis to cache session tokens." Which modal best expresses a practical possibility being recommended?
Could expresses a practical possibility or option in design discussions: "We could use Redis" — this invites consideration without being prescriptive. It signals "this is one valid approach we might take" rather than a decision. Compare: must (obligation — not appropriate for proposing options), will (decision already made — too assertive for an exploratory discussion), should (recommendation — stronger than could, implies the speaker thinks this is the right choice). In design meetings, "could" is used to table options; "should" to advocate for an option; "will" only after a decision. "We could use Redis, we could use Memcached, or we could keep it in the database — what are your thoughts?"
2 / 23
An engineer says: "Switching to async processing _____ reduce the p99 latency by roughly 40%." Which modal expresses a confident prediction based on evidence?
Would expresses a confident hypothetical outcome — a prediction about what will happen if a condition is met: "If we switch to async processing, it would reduce p99 latency by 40%." "Would" signals the speaker has evidence or reasoning behind the prediction and is reasonably confident. Might expresses a lower-confidence possibility: "it might reduce latency" — the speaker is uncertain. Could expresses general possibility without prediction: "it could reduce latency" — the speaker acknowledges it is possible but is not predicting. Use "would" when presenting benchmark data or analysis; "might" when speculating without data.
3 / 23
During a code review, an engineer comments: "This _____ cause a race condition if two threads access the cache simultaneously." Which modal is most appropriate?
Might is the correct choice for expressing a risk or speculation in code review: "This might cause a race condition" — the engineer is identifying a potential issue without claiming it will definitely happen. This is the appropriate epistemic register for code review comments: assertive enough to flag the concern, hedged enough to acknowledge it may not occur under all conditions. Will is too certain — implying the bug always triggers. Would is conditional — implies "if X then Y" (needs a condition). Must implies logical certainty or obligation, which is too strong for a potential concurrency risk. In code review, "might" and "could" are preferred for speculative concerns; "will" for definite issues.
4 / 23
A risk assessment states: "Deploying without feature flags _____ make rollback significantly more difficult." Which modal is most appropriate?
Would is the correct choice in a risk assessment when describing the consequence of an action: "Deploying without feature flags would make rollback more difficult" — the speaker is predicting a specific outcome of the proposed approach. This is the standard modal for consequence statements in risk sections of design docs and proposals: "This approach would introduce additional latency", "Removing the index would degrade query performance", "Skipping the migration step would break the foreign key constraint." "Might" and "could" introduce too much uncertainty for a risk that is clearly predictable. "Can" is too general — it expresses inherent capability, not consequence.
5 / 23
Which sentence correctly uses hypothetical language to hedge a recommendation in a technical proposal?
"We should consider adopting GraphQL, which would give clients more flexibility over data fetching" uses two modals correctly: should (recommendation — the speaker advocates for the action) and would (consequence — describing the benefit if the recommendation is followed). This is the ideal hypothetical register for a technical proposal: assertive enough to make a clear recommendation, hedged enough to acknowledge the decision has not been made. Option A uses "will" — too certain, sounds like an announcement, not a proposal. Option B uses "must" and implies catastrophe — too alarmist for a design proposal. Option D over-hedges with multiple stacked uncertainty markers — this sounds indecisive and is poor professional register.
6 / 23
John: 'If we refactor this module, it might improve performance, but there's no guarantee.' Which modal does he primarily use to express a potential benefit with significant uncertainty?
John is using conditional language ('if…then') to frame the refactoring as dependent on an uncertain outcome. The use of 'might' further emphasizes this lack of certainty and avoids making a definitive claim about performance improvement. The incorrect options all represent stronger statements or directives.
7 / 23
Sarah (in a Slack message): 'Assuming the database connection pool is properly configured, we should see a significant decrease in query execution times.' Which modal does she employ to suggest a likely outcome based on an assumption?
Sarah is using subjunctive language ('assuming') to introduce the dependence of her prediction on an unverified condition. This acknowledges that the decrease in query times isn't guaranteed and highlights the importance of proper configuration. The other options represent more assertive claims without acknowledging this assumption.
8 / 23
During a code review, Mark comments: 'If we implement this new authentication flow using JWTs, it could simplify the API but introduces potential security vulnerabilities if not handled carefully.' Which modal best captures his cautious recommendation?
Mark is using conditional language ('if') to frame his recommendation as contingent on careful implementation. He's acknowledging the potential benefits while immediately raising concerns about possible negative consequences. This demonstrates a balanced and cautious approach crucial for technical discussions.
9 / 23
David: 'If we scale the application horizontally, it could alleviate some of the performance bottlenecks we're seeing.' Which modal best expresses a potential solution with an element of uncertainty?
David is using conditional language ('if') to frame the horizontal scaling as a potential solution that might address performance bottlenecks. The use of 'could' indicates that this is not a guaranteed outcome and acknowledges the possibility that other factors are at play. It's a pragmatic suggestion acknowledging risk.
10 / 23
John: 'If we refactor this module, it might improve performance, but there's no guarantee.' Which modal does he primarily use to express a potential benefit with significant uncertainty?
John is using conditional language ('if…then') to frame the refactoring as dependent on an uncertain outcome. The use of 'might' further emphasizes this lack of certainty and avoids making a definitive claim about performance improvement. The incorrect options all represent stronger statements or directives.
11 / 23
Sarah (in a Slack message): 'Assuming the database connection pool is properly configured, we should see a significant decrease in query execution times.' Which modal does she employ to suggest a likely outcome based on an assumption?
Sarah is using subjunctive language ('assuming') to introduce the dependence of her prediction on an unverified condition. This acknowledges that the decrease in query times isn't guaranteed and highlights the importance of proper configuration. The other options represent more assertive claims without acknowledging this assumption.
12 / 23
During a code review, Mark comments: 'If we implement this new authentication flow using JWTs, it could simplify the API but introduces potential security vulnerabilities if not handled carefully.' Which modal best captures his cautious recommendation?
Mark is using conditional language ('if') to frame his recommendation as contingent on careful implementation. He's acknowledging the potential benefits while immediately raising concerns about possible negative consequences. This demonstrates a balanced and cautious approach crucial for technical discussions.
13 / 23
David: 'If we scale the application horizontally, it could alleviate some of the performance bottlenecks we're seeing.' Which modal best expresses a potential solution with an element of uncertainty?
David is using conditional language ('if') to frame the horizontal scaling as a potential solution that might address performance bottlenecks. The use of 'could' indicates that this is not a guaranteed outcome and acknowledges the possibility that other factors are at play. It's a pragmatic suggestion acknowledging risk.
14 / 23
John: 'If we refactor this module, it might improve performance, but there's no guarantee.' Which modal does he primarily use to express a potential benefit with significant uncertainty?
John is using conditional language ('if…then') to frame the refactoring as dependent on an uncertain outcome. The use of 'might' further emphasizes this lack of certainty and avoids making a definitive claim about performance improvement. The incorrect options all represent stronger statements or directives.
15 / 23
Sarah (in a Slack message): 'Assuming the database connection pool is properly configured, we should see a significant decrease in query execution times.' Which modal does she employ to suggest a likely outcome based on an assumption?
Sarah is using subjunctive language ('assuming') to introduce the dependence of her prediction on an unverified condition. This acknowledges that the decrease in query times isn't guaranteed and highlights the importance of proper configuration. The other options represent more assertive claims without acknowledging this assumption.
16 / 23
During a code review, Mark comments: 'If we implement this new authentication flow using JWTs, it could simplify the API but introduces potential security vulnerabilities if not handled carefully.' Which modal best captures his cautious recommendation?
Mark is using conditional language ('if') to frame his recommendation as contingent on careful implementation. He's acknowledging the potential benefits while immediately raising concerns about possible negative consequences. This demonstrates a balanced and cautious approach crucial for technical discussions.
17 / 23
David: 'If we scale the application horizontally, it could alleviate some of the performance bottlenecks we're seeing.' Which modal best expresses a potential solution with an element of uncertainty?
David is using conditional language ('if') to frame the horizontal scaling as a potential solution that might address performance bottlenecks. The use of 'could' indicates that this is not a guaranteed outcome and acknowledges the possibility that other factors are at play. It's a pragmatic suggestion acknowledging risk.
18 / 23
Reviewer comment: 'Assuming the API endpoint returns valid JSON, we can proceed with parsing it.' Is this a suitable use of hypothetical language in a code review context?
This comment uses 'assuming,' which introduces a condition. However, as stated, it's too vague. A better approach would clearly define what constitutes 'valid JSON' and the expected response, rather than relying on an unverified assumption. The question tests understanding of hedging language in a practical code review scenario.
19 / 23
During a standup meeting, Alex says: 'If we deploy the new feature tonight, it *could* expose us to some unexpected load spikes. We should monitor closely.' Which modal does he primarily use to express a potential negative consequence with an element of uncertainty?
Alex uses 'could' which signals a hypothetical scenario. The key here isn't simply acknowledging potential problems (option A), but recognizing that the outcome is uncertain and depends on monitoring. 'Speculative' highlights the uncertainty, while 'definitive' contradicts the cautious tone. The correct answer emphasizes the speaker's reliance on observation.
20 / 23
In a PR description for a new microservice, Emily writes: 'Assuming the network latency remains stable, this service should improve response times by approximately 15%.' What type of hypothetical language is she employing?
Emily's statement relies on a 'assuming' clause. This signifies that the 15% improvement is predicated on a specific condition (stable network latency) holding true. 'Counterfactual' describes an unreal scenario, 'probabilistic' suggests a degree of certainty absent here, and 'deterministic' is entirely inappropriate given the potential for external factors.
21 / 23
Sarah writes in a Slack message: 'Assuming the database schema remains unchanged, migrating to this new version should be relatively straightforward.' What aspect of hypothetical language is Sarah primarily focused on?
Sarah's use of 'assuming' highlights a critical element of risk mitigation. The statement acknowledges a dependency (unchanged schema) that *must* hold true for the migration to be simple. While scenario analysis is relevant, Sarah's focus is on proactively addressing a potential issue.
22 / 23
Reviewer comment: 'Assuming the API endpoint returns valid JSON, we can proceed with parsing it.' Is this a suitable use of hypothetical language in a code review context?
A. It's an overly cautious statement, best phrased as a direct confirmation. B. It's appropriate because the reviewer is stating what *should* happen under ideal conditions, acknowledging potential issues but proceeding based on the assumption. C. It's technically incorrect; API responses should always be validated regardless of their format. D. This statement clearly indicates a bug and requires immediate attention.
The reviewer's comment uses 'assuming' to express a conditional outcome – what *should* happen if the JSON is valid. This is standard hypothetical language in code reviews when considering potential issues while still moving forward with parsing. Options A and C misinterpret the intention; option D is too strong.
23 / 23
Mark comments: 'If we implement this new authentication flow using JWTs, it could simplify the API but introduces potential security vulnerabilities if not handled carefully.' Which modal best expresses a potential benefit alongside an acknowledgement of risk?
A. He's stating the only possible outcome is simplification B. He's offering a balanced assessment, highlighting both the positive (simplification) and negative (vulnerabilities) aspects with conditional language. C. He's demanding immediate action to implement JWTs. D. He's dismissing concerns about security vulnerabilities.
Mark's use of 'if…it could' demonstrates a balanced assessment. The phrasing acknowledges the potential benefit (simplification) while simultaneously introducing a risk (vulnerabilities), using conditional language to manage expectations.
What will I practise in "Hypothetical Language in Technical Discussions — Grammar Exercise"?
Practise would, could, might in design discussions, risk assessments, and proposals. 5 exercises on modal nuance for IT professionals.
How many exercises are in this module?
This module has 23 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.