5 exercises — choose the right word when several seem correct: bug vs defect, feature vs functionality, fix vs resolve, update vs upgrade, deprecate vs remove.
Why precision matters in IT English
bug / defect / issue / error — same problem, different formality and precision
feature / functionality / capability — scoped vs. broad vs. organisational
fix / resolve / address / patch — how thoroughly you solved the problem
update / upgrade / patch — magnitude of the change
deprecated / removed / disabled — where in the retirement lifecycle
0 / 25 completed
1 / 25
A team writes a bug report. Which term is most appropriate in a formal QA report submitted to a client? "We identified three ___ in the payment module."
Bug vs. Defect vs. Issue vs. Error — subtle but real differences:
Bug: Informal term for an unintended flaw in code. "We found a bug in the login flow." Universally understood, slightly informal.
Defect: The formal QA/testing term. A defect is a deviation from the requirement. Used in test reports, client contracts, and SLA documents. "3 critical defects were identified during UAT."
Issue: Deliberately vague — can mean a bug, a limitation, a configuation problem, or a disagreement. GitHub calls everything an "issue" for this reason. In formal writing, prefer something more specific.
Error: Technical — the incorrect output produced by the system. A 500 error, a validation error, a parsing error. "The function returns an error if the input is null." Also used for human mistakes: "human error".
In a client-facing QA report: defect is the standard formal term. In Jira/GitHub: issue or bug. In code: error.
2 / 25
A product manager is writing a specification document. Which sentence uses the most precise vocabulary?
Feature vs. Functionality vs. Capability:
Feature: A specific, named unit of product value that a user can interact with. "The export feature", "the dark mode feature", "the search feature." Features are scoped, deliverable, and user-visible. Best in product specs and user stories.
Functionality: The general ability of a system to perform a set of actions. Broader than a feature — "the system's search functionality" (all the things search can do). Slightly more technical. Often overused, making sentences vague: "provide the functionality to" can usually be replaced with a cleaner verb.
Capability: Even broader — organisational or system-level. "The platform has real-time collaboration capabilities." Often used in RFPs, enterprise sales, and high-level architecture docs. More formal than "feature".
Best practice: Use "feature" for a specific user-visible deliverable. Use "functionality" when you mean a whole area of behaviour. Avoid mixing all three in the same sentence — it sounds padded. Option B is simplest and clearest.
3 / 25
In a pull request description, a developer writes: "This PR ___ the race condition in the session handler." Which verb choice sounds most professional and precise?
Fix vs. Resolve vs. Address vs. Patch — register and precision differences:
Fix: The most common term. Direct, informal, widely used. "I fixed the bug." Fine in Slack and most PRs, but slightly too casual for incident reports or client communication.
Resolve: Implies a proper, complete solution after investigation. "The incident was resolved at 14:35 UTC." Standard in post-mortems, SLA communications, and incident tickets. More formal than "fix".
Address: Deliberately careful — means "deal with / take action on" without guaranteeing complete elimination. "This PR addresses the race condition" = we tackled it, but use "resolve" once it is definitively fixed. Common when there may be remaining edge cases.
Patch: Suggests a targeted, sometimes temporary fix — often a workaround rather than a root-cause solution. "We patched the vulnerability" (security). "hotfix" or "patch release". Use when the fix is specifically surgical/minimal.
For a PR dealing with a race condition properly: resolves is the best choice — it signals thorough work.
4 / 25
A release note says: "Node.js 22.0.0 is now available. This is a major ___ from version 20." Which word completes the sentence correctly?
Update vs. Upgrade vs. Patch vs. Release:
Update: Generic term — any change applied to software. Can be small or large. "You have 3 updates available." Neutral, broad, informal. Often used for minor/patch-level changes.
Upgrade: A move to a significantly newer or higher version — usually implies a deliberate migration, potential breaking changes, effort required. "We need to upgrade from Python 3.9 to 3.12." A major version bump is an upgrade.
Patch: A small, targeted fix — specifically the third number in semantic versioning (MAJOR.MINOR.PATCH). "We released a patch for the XSS vulnerability." Also used for operating system security patches.
Release: The act of publishing any version to users. "The new release includes…" — general, covers all types.
Semantic versioning guide: 22.0.0 → 20.x.x is a major upgrade (breaking changes possible). 22.0.0 → 22.1.0 is a minor update. 22.0.0 → 22.0.1 is a patch.
5 / 25
A platform team announcement says: "The v1 API will be deprecated in Q2 and removed in Q4." What is the difference between deprecated and removed?
Deprecate vs. Remove vs. Sunset vs. Disable — a critical sequence:
Deprecated: Still functional — but officially marked as "use this at your own risk, we may remove it." A deprecation notice means: "we recommend you migrate, we will no longer add features, and we plan to remove this." A grace period follows so clients can migrate. The API still works during Q2–Q3.
Removed / Sunset: Actually gone — calling the endpoint returns 404 / 410 Gone. This is the end of the grace period.
Disabled: Turned off but not deleted — often used for feature flags, configuration toggles, or temporarily suspended access.
The standard sequence: Ship → Maintain → Deprecate (announce retirement) → Sunset/Remove → (optionally) Delete source code.
In real life: "The v1 API is deprecated as of March 2026" means it still works but clients should migrate. "The v1 API has been removed" means it will return an error. Clients need to know this difference to prioritise their migration work.
6 / 25
Sarah from the backend team is reviewing a pull request submitted by Mark. Mark has written: 'This change improves performance and reduces latency.' During the code review, another developer, David, asks her to clarify. Which of the following phrases would be the most appropriate for Sarah to use when explaining the impact of Mark's changes?
While 'faster' and 'less slow' are understandable approximations, they lack the precision needed in a technical context. 'The response times are significantly better now' provides a measurable metric—latency—directly related to performance improvements. Using terms like 'optimized' is too vague; David needs specifics. 'This directly addresses the performance bottleneck' demonstrates a deeper understanding of the issue and its resolution, which is more professional.
7 / 25
Mark writes in a PR description: 'This feature enhances the user experience and streamlines the workflow.' During a discussion with his team lead, Emily asks him to elaborate. Which of the following phrases best captures the meaning of Mark's statement?
The key here is understanding that 'refined' accurately conveys a nuanced improvement without implying drastic changes. Options A and B suggest major overhauls, while option C implies minor tweaking. 'Optimized' leans heavily into performance metrics which Mark doesn't explicitly state. Using 'refined' acknowledges the statement's focus on usability and workflow without exaggeration – a common professional approach in software development discussions.
8 / 25
Liam: 'The new service mesh implementation significantly reduced our operational overhead.'
Chloe (asking for clarification): 'Could you elaborate on what specifically you mean by 'operational overhead' in this context?' Which of the following phrases best reflects Chloe's request?
Chloe is seeking a more precise definition of 'operational overhead,' which can be vague. Option A focuses on deployments, while option B offers a superficial interpretation. Option 3 correctly identifies the key elements – monitoring, incident response, and configuration management – representing the technical aspects involved in maintaining a service. Option 4 is too focused on automation and doesn't address the core meaning of the phrase.
9 / 25
Alex: 'We're seeing some performance degradation with the new image processing pipeline. It's taking noticeably longer to generate thumbnails.'
Ben (responding in Slack): 'Okay, can you quantify that? Like, what's the actual impact on response times?'
The question focuses on the subtle difference between describing an issue (Alex's statement) and requesting specific information to assess it properly. Ben isn't dismissing Alex's concern; he's pushing for quantifiable results – a crucial aspect of technical discussions in development. The key is that 'quantify' implies needing a numerical measurement, differentiating this from simply stating a negative experience.
10 / 25
# Scenario: A developer is reviewing a Slack message from a junior engineer.
Mark (Junior Engineer): "This refactor improves the efficiency of the data retrieval process." During a code review, you need to give Mark feedback. Which of the following responses best communicates your understanding and asks for further details?
Option A: "Sounds good! Just make sure it's fast enough."
Option B: "Can you elaborate on what specifically you mean by 'efficiency' in this context? What metrics are being improved, and how were they measured?"
Option C: "That's a great improvement. Let's just keep an eye on the performance."
Option D: "Okay, let's test it to see if it really is more efficient."
The key here is understanding that 'efficiency' in software development can mean different things – faster execution, reduced resource usage, or simpler code. Option B directly asks for clarification on the *specific* meaning of 'efficiency', prompting Mark to explain his reasoning and provide quantifiable evidence. Options A and C are too vague and don't encourage deeper discussion, while option D focuses solely on testing without understanding the initial claim.
11 / 25
Sarah from the backend team is reviewing a pull request submitted by Mark. Mark has written: 'This change improves performance and reduces latency.' During the code review, another developer, David, asks her to clarify. Which of the following phrases would be the most appropriate for Sarah to use when explaining the impact of Mark's changes?
While 'faster' and 'less slow' are understandable approximations, they lack the precision needed in a technical context. 'The response times are significantly better now' provides a measurable metric—latency—directly related to performance improvements. Using terms like 'optimized' is too vague; David needs specifics. 'This directly addresses the performance bottleneck' demonstrates a deeper understanding of the issue and its resolution, which is more professional.
12 / 25
Mark writes in a PR description: 'This feature enhances the user experience and streamlines the workflow.' During a discussion with his team lead, Emily asks him to elaborate. Which of the following phrases best captures the meaning of Mark's statement?
The key here is understanding that 'refined' accurately conveys a nuanced improvement without implying drastic changes. Options A and B suggest major overhauls, while option C implies minor tweaking. 'Optimized' leans heavily into performance metrics which Mark doesn't explicitly state. Using 'refined' acknowledges the statement's focus on usability and workflow without exaggeration – a common professional approach in software development discussions.
13 / 25
Liam: 'The new service mesh implementation significantly reduced our operational overhead.'
Chloe (asking for clarification): 'Could you elaborate on what specifically you mean by 'operational overhead' in this context?' Which of the following phrases best reflects Chloe's request?
Chloe is seeking a more precise definition of 'operational overhead,' which can be vague. Option A focuses on deployments, while option B offers a superficial interpretation. Option 3 correctly identifies the key elements – monitoring, incident response, and configuration management – representing the technical aspects involved in maintaining a service. Option 4 is too focused on automation and doesn't address the core meaning of the phrase.
14 / 25
Alex: 'We're seeing some performance degradation with the new image processing pipeline. It's taking noticeably longer to generate thumbnails.'
Ben (responding in Slack): 'Okay, can you quantify that? Like, what's the actual impact on response times?'
The question focuses on the subtle difference between describing an issue (Alex's statement) and requesting specific information to assess it properly. Ben isn't dismissing Alex's concern; he's pushing for quantifiable results – a crucial aspect of technical discussions in development. The key is that 'quantify' implies needing a numerical measurement, differentiating this from simply stating a negative experience.
15 / 25
# Scenario: A developer is reviewing a Slack message from a junior engineer.
Mark (Junior Engineer): "This refactor improves the efficiency of the data retrieval process." During a code review, you need to give Mark feedback. Which of the following responses best communicates your understanding and asks for further details?
Option A: "Sounds good! Just make sure it's fast enough."
Option B: "Can you elaborate on what specifically you mean by 'efficiency' in this context? What metrics are being improved, and how were they measured?"
Option C: "That's a great improvement. Let's just keep an eye on the performance."
Option D: "Okay, let's test it to see if it really is more efficient."
The key here is understanding that 'efficiency' in software development can mean different things – faster execution, reduced resource usage, or simpler code. Option B directly asks for clarification on the *specific* meaning of 'efficiency', prompting Mark to explain his reasoning and provide quantifiable evidence. Options A and C are too vague and don't encourage deeper discussion, while option D focuses solely on testing without understanding the initial claim.
16 / 25
Sarah from the backend team is reviewing a pull request submitted by Mark. Mark has written: 'This change improves performance and reduces latency.' During the code review, another developer, David, asks her to clarify. Which of the following phrases would be the most appropriate for Sarah to use when explaining the impact of Mark's changes?
While 'faster' and 'less slow' are understandable approximations, they lack the precision needed in a technical context. 'The response times are significantly better now' provides a measurable metric—latency—directly related to performance improvements. Using terms like 'optimized' is too vague; David needs specifics. 'This directly addresses the performance bottleneck' demonstrates a deeper understanding of the issue and its resolution, which is more professional.
17 / 25
Mark writes in a PR description: 'This feature enhances the user experience and streamlines the workflow.' During a discussion with his team lead, Emily asks him to elaborate. Which of the following phrases best captures the meaning of Mark's statement?
The key here is understanding that 'refined' accurately conveys a nuanced improvement without implying drastic changes. Options A and B suggest major overhauls, while option C implies minor tweaking. 'Optimized' leans heavily into performance metrics which Mark doesn't explicitly state. Using 'refined' acknowledges the statement's focus on usability and workflow without exaggeration – a common professional approach in software development discussions.
18 / 25
Liam: 'The new service mesh implementation significantly reduced our operational overhead.'
Chloe (asking for clarification): 'Could you elaborate on what specifically you mean by 'operational overhead' in this context?' Which of the following phrases best reflects Chloe's request?
Chloe is seeking a more precise definition of 'operational overhead,' which can be vague. Option A focuses on deployments, while option B offers a superficial interpretation. Option 3 correctly identifies the key elements – monitoring, incident response, and configuration management – representing the technical aspects involved in maintaining a service. Option 4 is too focused on automation and doesn't address the core meaning of the phrase.
19 / 25
Alex: 'We're seeing some performance degradation with the new image processing pipeline. It's taking noticeably longer to generate thumbnails.'
Ben (responding in Slack): 'Okay, can you quantify that? Like, what's the actual impact on response times?'
The question focuses on the subtle difference between describing an issue (Alex's statement) and requesting specific information to assess it properly. Ben isn't dismissing Alex's concern; he's pushing for quantifiable results – a crucial aspect of technical discussions in development. The key is that 'quantify' implies needing a numerical measurement, differentiating this from simply stating a negative experience.
20 / 25
# Scenario: A developer is reviewing a Slack message from a junior engineer.
Mark (Junior Engineer): "This refactor improves the efficiency of the data retrieval process." During a code review, you need to give Mark feedback. Which of the following responses best communicates your understanding and asks for further details?
Option A: "Sounds good! Just make sure it's fast enough."
Option B: "Can you elaborate on what specifically you mean by 'efficiency' in this context? What metrics are being improved, and how were they measured?"
Option C: "That's a great improvement. Let's just keep an eye on the performance."
Option D: "Okay, let's test it to see if it really is more efficient."
The key here is understanding that 'efficiency' in software development can mean different things – faster execution, reduced resource usage, or simpler code. Option B directly asks for clarification on the *specific* meaning of 'efficiency', prompting Mark to explain his reasoning and provide quantifiable evidence. Options A and C are too vague and don't encourage deeper discussion, while option D focuses solely on testing without understanding the initial claim.
21 / 25
Sarah from the backend team is reviewing a pull request submitted by Mark. Mark has written: 'This change improves performance and reduces latency.' During the code review, another developer, David, asks her to clarify. Which of the following phrases would be the most appropriate for Sarah to use when explaining the impact of Mark's changes?
While 'faster' and 'less slow' are understandable approximations, they lack the precision needed in a technical context. 'The response times are significantly better now' provides a measurable metric—latency—directly related to performance improvements. Using terms like 'optimized' is too vague; David needs specifics. 'This directly addresses the performance bottleneck' demonstrates a deeper understanding of the issue and its resolution, which is more professional.
22 / 25
Mark writes in a PR description: 'This feature enhances the user experience and streamlines the workflow.' During a discussion with his team lead, Emily asks him to elaborate. Which of the following phrases best captures the meaning of Mark's statement?
The key here is understanding that 'refined' accurately conveys a nuanced improvement without implying drastic changes. Options A and B suggest major overhauls, while option C implies minor tweaking. 'Optimized' leans heavily into performance metrics which Mark doesn't explicitly state. Using 'refined' acknowledges the statement's focus on usability and workflow without exaggeration – a common professional approach in software development discussions.
23 / 25
Liam: 'The new service mesh implementation significantly reduced our operational overhead.'
Chloe (asking for clarification): 'Could you elaborate on what specifically you mean by 'operational overhead' in this context?' Which of the following phrases best reflects Chloe's request?
Chloe is seeking a more precise definition of 'operational overhead,' which can be vague. Option A focuses on deployments, while option B offers a superficial interpretation. Option 3 correctly identifies the key elements – monitoring, incident response, and configuration management – representing the technical aspects involved in maintaining a service. Option 4 is too focused on automation and doesn't address the core meaning of the phrase.
24 / 25
Alex: 'We're seeing some performance degradation with the new image processing pipeline. It's taking noticeably longer to generate thumbnails.'
Ben (responding in Slack): 'Okay, can you quantify that? Like, what's the actual impact on response times?'
The question focuses on the subtle difference between describing an issue (Alex's statement) and requesting specific information to assess it properly. Ben isn't dismissing Alex's concern; he's pushing for quantifiable results – a crucial aspect of technical discussions in development. The key is that 'quantify' implies needing a numerical measurement, differentiating this from simply stating a negative experience.
25 / 25
# Scenario: A developer is reviewing a Slack message from a junior engineer.
Mark (Junior Engineer): "This refactor improves the efficiency of the data retrieval process." During a code review, you need to give Mark feedback. Which of the following responses best communicates your understanding and asks for further details?
Option A: "Sounds good! Just make sure it's fast enough."
Option B: "Can you elaborate on what specifically you mean by 'efficiency' in this context? What metrics are being improved, and how were they measured?"
Option C: "That's a great improvement. Let's just keep an eye on the performance."
Option D: "Okay, let's test it to see if it really is more efficient."
The key here is understanding that 'efficiency' in software development can mean different things – faster execution, reduced resource usage, or simpler code. Option B directly asks for clarification on the *specific* meaning of 'efficiency', prompting Mark to explain his reasoning and provide quantifiable evidence. Options A and C are too vague and don't encourage deeper discussion, while option D focuses solely on testing without understanding the initial claim.
What does the "Near-Synonyms & Subtle Differences — IT English" exercise cover?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.
How many questions are in "Near-Synonyms & Subtle Differences — IT English"?
This exercise has 25 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more False Friends & Tricky Words exercises?
Browse the full False Friends & Tricky Words hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.