Intermediate
Grammar
#discourse
#cohesion
"Then Again" for Self-Reconsideration
5 exercises — practise softening an earlier claim with the comment clause "then again".
0 / 35 completed
1 / 35
Which sentence correctly uses "then again" to introduce a second thought after stating a plan?
"Then again, a staged rollout would limit the blast radius" correctly opens with the fixed two-word phrase "then again" followed by a comma. Options B, C, and D all reorder or pad the fixed phrase incorrectly.
2 / 35
Which sentence correctly uses "then again" mid-paragraph to reconsider a stated preference?
"...the managed service; then again, given our budget constraints..." correctly preserves the two-word fixed phrase. Options B, C, and D reorder or repeat words within the fixed phrase, which is ungrammatical.
3 / 35
Which sentence correctly distinguishes "then again" (a self-reflective second thought that softens the first claim) from "on the other hand" (a more neutral, balanced presentation of two sides)?
"On the other hand, some teams prefer monorepos... then again, maybe I am overestimating..." correctly uses "on the other hand" to present the balanced comparison first, then "then again" to add a self-doubting second thought. Options B, C, and D swap or merge the two phrases incoherently.
4 / 35
Which sentence correctly uses "then again" to reconsider a criticism just made about a tool?
"Then again, it did catch a real bug in my last pull request" is the only option with the standard fixed order. Options B and D insert extra words into the phrase. Option C reverses the word order, which changes the meaning to a plain repetition rather than the idiom.
5 / 35
Which sentence correctly uses "then again" to soften an earlier confident claim about a root cause?
"Then again, we have not ruled out a clock skew issue" correctly keeps "then again" as a single unbroken unit followed by one comma. Option B misplaces the comma inside the following clause. Option C wrongly splits "then" and "again" with a comma. Option D reverses the fixed word order.
6 / 35
Alex: "I'm going to refactor the entire user authentication module this week. It's a mess!"
Ben (in a code review comment): "Then again, the current implementation is surprisingly stable and hasn't had any reported issues."The key here is understanding 'then again' as a softening introduction of a counter-argument. Ben isn't dismissing Alex's concern about the messiness; he's acknowledging it while presenting evidence that contradicts the immediate need for a full refactor. Options A and C are too extreme, and option D is unnecessarily aggressive.
7 / 35
Sarah (in a Slack message to her team): "I'm convinced the slow database queries are due to inefficient indexing. We need to redesign them immediately!"
Which of the following best uses 'then again' in response?'Then again' here serves as a gentle pause and invitation to reconsider the immediate conclusion. Sarah's statement is forceful; 'then again' introduces the possibility of another factor – increased data volume – that might be responsible for the slow queries. Options A and C are too dismissive, and option D misses the opportunity for nuanced discussion.
8 / 35
David (in a PR description): "This commit fixes the critical memory leak. The code was fundamentally flawed and required a complete rewrite."'Then again' here softens David's initial assertion about the code being 'fundamentally flawed.' It acknowledges the complexity while also recognizing a positive outcome – an elegant solution. This demonstrates self-reconsideration and avoids sounding overly judgmental, which is valuable in technical discussions.
9 / 35
Maria (during a standup update): "I spent all morning debugging the authentication service. It was a nightmare! The root cause was a misconfigured server setting."'Then again' here shifts the focus from the initial frustration to a positive outcome – the discovery of a valuable insight. This demonstrates self-reconsideration by recognizing that even a frustrating debugging session can lead to learning and prevent future issues. It's about framing the experience constructively.
10 / 35
Tom (responding to feedback on his API design): "I designed this endpoint with a simple GET request – it's the most efficient approach!"'Then again' here introduces a thoughtful counterpoint – suggesting that while GET might be efficient now, supporting POST could offer more flexibility for future development. It's not dismissing the initial claim but acknowledging a potential alternative and inviting further discussion about long-term design needs.
11 / 35
Alex: "I'm going to refactor the entire user authentication module this week. It's a mess!"
Ben (in a code review comment): "Then again, the current implementation is surprisingly stable and hasn't had any reported issues."The key here is understanding 'then again' as a softening introduction of a counter-argument. Ben isn't dismissing Alex's concern about the messiness; he's acknowledging it while presenting evidence that contradicts the immediate need for a full refactor. Options A and C are too extreme, and option D is unnecessarily aggressive.
12 / 35
Sarah (in a Slack message to her team): "I'm convinced the slow database queries are due to inefficient indexing. We need to redesign them immediately!"
Which of the following best uses 'then again' in response?'Then again' here serves as a gentle pause and invitation to reconsider the immediate conclusion. Sarah's statement is forceful; 'then again' introduces the possibility of another factor – increased data volume – that might be responsible for the slow queries. Options A and C are too dismissive, and option D misses the opportunity for nuanced discussion.
13 / 35
David (in a PR description): "This commit fixes the critical memory leak. The code was fundamentally flawed and required a complete rewrite."'Then again' here softens David's initial assertion about the code being 'fundamentally flawed.' It acknowledges the complexity while also recognizing a positive outcome – an elegant solution. This demonstrates self-reconsideration and avoids sounding overly judgmental, which is valuable in technical discussions.
14 / 35
Maria (during a standup update): "I spent all morning debugging the authentication service. It was a nightmare! The root cause was a misconfigured server setting."'Then again' here shifts the focus from the initial frustration to a positive outcome – the discovery of a valuable insight. This demonstrates self-reconsideration by recognizing that even a frustrating debugging session can lead to learning and prevent future issues. It's about framing the experience constructively.
15 / 35
Tom (responding to feedback on his API design): "I designed this endpoint with a simple GET request – it's the most efficient approach!"'Then again' here introduces a thoughtful counterpoint – suggesting that while GET might be efficient now, supporting POST could offer more flexibility for future development. It's not dismissing the initial claim but acknowledging a potential alternative and inviting further discussion about long-term design needs.
16 / 35
Alex: "I'm going to refactor the entire user authentication module this week. It's a mess!"
Ben (in a code review comment): "Then again, the current implementation is surprisingly stable and hasn't had any reported issues."The key here is understanding 'then again' as a softening introduction of a counter-argument. Ben isn't dismissing Alex's concern about the messiness; he's acknowledging it while presenting evidence that contradicts the immediate need for a full refactor. Options A and C are too extreme, and option D is unnecessarily aggressive.
17 / 35
Sarah (in a Slack message to her team): "I'm convinced the slow database queries are due to inefficient indexing. We need to redesign them immediately!"
Which of the following best uses 'then again' in response?'Then again' here serves as a gentle pause and invitation to reconsider the immediate conclusion. Sarah's statement is forceful; 'then again' introduces the possibility of another factor – increased data volume – that might be responsible for the slow queries. Options A and C are too dismissive, and option D misses the opportunity for nuanced discussion.
18 / 35
David (in a PR description): "This commit fixes the critical memory leak. The code was fundamentally flawed and required a complete rewrite."'Then again' here softens David's initial assertion about the code being 'fundamentally flawed.' It acknowledges the complexity while also recognizing a positive outcome – an elegant solution. This demonstrates self-reconsideration and avoids sounding overly judgmental, which is valuable in technical discussions.
19 / 35
Maria (during a standup update): "I spent all morning debugging the authentication service. It was a nightmare! The root cause was a misconfigured server setting."'Then again' here shifts the focus from the initial frustration to a positive outcome – the discovery of a valuable insight. This demonstrates self-reconsideration by recognizing that even a frustrating debugging session can lead to learning and prevent future issues. It's about framing the experience constructively.
20 / 35
Tom (responding to feedback on his API design): "I designed this endpoint with a simple GET request – it's the most efficient approach!"'Then again' here introduces a thoughtful counterpoint – suggesting that while GET might be efficient now, supporting POST could offer more flexibility for future development. It's not dismissing the initial claim but acknowledging a potential alternative and inviting further discussion about long-term design needs.
21 / 35
Alex: "I'm going to refactor the entire user authentication module this week. It's a mess!"
Ben (in a code review comment): "Then again, the current implementation is surprisingly stable and hasn't had any reported issues."The key here is understanding 'then again' as a softening introduction of a counter-argument. Ben isn't dismissing Alex's concern about the messiness; he's acknowledging it while presenting evidence that contradicts the immediate need for a full refactor. Options A and C are too extreme, and option D is unnecessarily aggressive.
22 / 35
Sarah (in a Slack message to her team): "I'm convinced the slow database queries are due to inefficient indexing. We need to redesign them immediately!"
Which of the following best uses 'then again' in response?'Then again' here serves as a gentle pause and invitation to reconsider the immediate conclusion. Sarah's statement is forceful; 'then again' introduces the possibility of another factor – increased data volume – that might be responsible for the slow queries. Options A and C are too dismissive, and option D misses the opportunity for nuanced discussion.
23 / 35
David (in a PR description): "This commit fixes the critical memory leak. The code was fundamentally flawed and required a complete rewrite."'Then again' here softens David's initial assertion about the code being 'fundamentally flawed.' It acknowledges the complexity while also recognizing a positive outcome – an elegant solution. This demonstrates self-reconsideration and avoids sounding overly judgmental, which is valuable in technical discussions.
24 / 35
Maria (during a standup update): "I spent all morning debugging the authentication service. It was a nightmare! The root cause was a misconfigured server setting."'Then again' here shifts the focus from the initial frustration to a positive outcome – the discovery of a valuable insight. This demonstrates self-reconsideration by recognizing that even a frustrating debugging session can lead to learning and prevent future issues. It's about framing the experience constructively.
25 / 35
Tom (responding to feedback on his API design): "I designed this endpoint with a simple GET request – it's the most efficient approach!"'Then again' here introduces a thoughtful counterpoint – suggesting that while GET might be efficient now, supporting POST could offer more flexibility for future development. It's not dismissing the initial claim but acknowledging a potential alternative and inviting further discussion about long-term design needs.
26 / 35
Alex: "I'm going to refactor the entire user authentication module this week. It's a mess!"
Ben (in a code review comment): "Then again, the current implementation is surprisingly stable and hasn't had any reported issues."The key here is understanding 'then again' as a softening introduction of a counter-argument. Ben isn't dismissing Alex's concern about the messiness; he's acknowledging it while presenting evidence that contradicts the immediate need for a full refactor. Options A and C are too extreme, and option D is unnecessarily aggressive.
27 / 35
Sarah (in a Slack message to her team): "I'm convinced the slow database queries are due to inefficient indexing. We need to redesign them immediately!"
Which of the following best uses 'then again' in response?'Then again' here serves as a gentle pause and invitation to reconsider the immediate conclusion. Sarah's statement is forceful; 'then again' introduces the possibility of another factor – increased data volume – that might be responsible for the slow queries. Options A and C are too dismissive, and option D misses the opportunity for nuanced discussion.
28 / 35
David (in a PR description): "This commit fixes the critical memory leak. The code was fundamentally flawed and required a complete rewrite."'Then again' here softens David's initial assertion about the code being 'fundamentally flawed.' It acknowledges the complexity while also recognizing a positive outcome – an elegant solution. This demonstrates self-reconsideration and avoids sounding overly judgmental, which is valuable in technical discussions.
29 / 35
Maria (during a standup update): "I spent all morning debugging the authentication service. It was a nightmare! The root cause was a misconfigured server setting."'Then again' here shifts the focus from the initial frustration to a positive outcome – the discovery of a valuable insight. This demonstrates self-reconsideration by recognizing that even a frustrating debugging session can lead to learning and prevent future issues. It's about framing the experience constructively.
30 / 35
Tom (responding to feedback on his API design): "I designed this endpoint with a simple GET request – it's the most efficient approach!"'Then again' here introduces a thoughtful counterpoint – suggesting that while GET might be efficient now, supporting POST could offer more flexibility for future development. It's not dismissing the initial claim but acknowledging a potential alternative and inviting further discussion about long-term design needs.
31 / 35
Alex: "I'm going to refactor the entire user authentication module this week. It's a mess!"
Ben (in a code review comment): "Then again, the current implementation is surprisingly stable and hasn't had any reported issues."The key here is understanding 'then again' as a softening introduction of a counter-argument. Ben isn't dismissing Alex's concern about the messiness; he's acknowledging it while presenting evidence that contradicts the immediate need for a full refactor. Options A and C are too extreme, and option D is unnecessarily aggressive.
32 / 35
Sarah (in a Slack message to her team): "I'm convinced the slow database queries are due to inefficient indexing. We need to redesign them immediately!"
Which of the following best uses 'then again' in response?'Then again' here serves as a gentle pause and invitation to reconsider the immediate conclusion. Sarah's statement is forceful; 'then again' introduces the possibility of another factor – increased data volume – that might be responsible for the slow queries. Options A and C are too dismissive, and option D misses the opportunity for nuanced discussion.
33 / 35
David (in a PR description): "This commit fixes the critical memory leak. The code was fundamentally flawed and required a complete rewrite."'Then again' here softens David's initial assertion about the code being 'fundamentally flawed.' It acknowledges the complexity while also recognizing a positive outcome – an elegant solution. This demonstrates self-reconsideration and avoids sounding overly judgmental, which is valuable in technical discussions.
34 / 35
Maria (during a standup update): "I spent all morning debugging the authentication service. It was a nightmare! The root cause was a misconfigured server setting."'Then again' here shifts the focus from the initial frustration to a positive outcome – the discovery of a valuable insight. This demonstrates self-reconsideration by recognizing that even a frustrating debugging session can lead to learning and prevent future issues. It's about framing the experience constructively.
35 / 35
Tom (responding to feedback on his API design): "I designed this endpoint with a simple GET request – it's the most efficient approach!"'Then again' here introduces a thoughtful counterpoint – suggesting that while GET might be efficient now, supporting POST could offer more flexibility for future development. It's not dismissing the initial claim but acknowledging a potential alternative and inviting further discussion about long-term design needs.
Next up:
More Grammar Exercises →
Frequently Asked Questions
What will I practise in ""Then Again" for Self-Reconsideration — IT Grammar Exercise"?
Practise using the fixed adverbial "then again" to introduce a self-reflective second thought that softens an earlier claim, distinct from the more neutral "on
How many exercises are in this module?
This module has 35 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.