5 exercises — choosing the right verb aspect (simple, progressive, perfect) in status updates, standups, release notes, and Slack messages.
0 / 20 completed
1 / 20
In a standup Slack message, your team writes: "_____ the new authentication service to staging." Which form is best?
In standup updates that report completed actions, the present perfect ("We have deployed") signals that the action is finished and relevant to the current state. The simple present ("We deploy") describes habitual actions. The present progressive ("We are deploying") signals an action still in progress. When the deployment is complete and you are reporting it, use have + past participle.
2 / 20
A status page reads: "Our engineers _____ the database issue right now. ETA: 30 minutes." Which form correctly signals ongoing work?
The present progressive ("are investigating") is the correct choice because it signals an action happening at this exact moment. The phrase "right now" and the given ETA confirm the action is still in progress. The simple present ("investigate") would sound like a permanent habit. The present perfect ("have investigated") would imply the work is already done, contradicting the ETA.
3 / 20
A release note says: "Version 2.4 _____ support for dark mode, improved API rate limiting, and bug fixes." Which aspect correctly describes features included in this release?
Release notes conventionally use the simple present to describe what a version includes or does. This is called the "release note present" — it describes the state of the software as delivered. "Is adding" implies an ongoing process, which is inappropriate for a finished release. "Has added" is also possible but less common in release-note style. "Adds" is the industry-standard choice for version changelogs.
4 / 20
During a sprint retrospective, the team lead says: "We _____ three major features this sprint." Which form summarises the sprint output?
The present perfect ("have delivered") is used to report the result of a completed activity that has present relevance — perfect for a retrospective looking back at a finished sprint. It connects past actions to the current moment (the end of the sprint). The simple past ("delivered") is also grammatically correct but the present perfect is preferred in British English for recent completed actions with current relevance.
5 / 20
An architecture decision record (ADR) states: "The team _____ PostgreSQL for all new microservices since Q1." Which form correctly shows an ongoing policy started in the past?
The present perfect with a time expression like "since Q1" describes an action or state that began in the past and continues to the present. "Has used" confirms that this practice started in Q1 and is still in effect now. The simple past ("used") would imply the practice has ended. The simple present ("uses") does not convey the historical starting point that "since Q1" requires.
6 / 20
Reviewer: 'I'm seeing that the payment gateway integration is still running. It seems like you're processing payments in a progressive form. Could you provide more details on the ongoing transaction flow?'
The key here is understanding that 'processing' indicates an action *currently* underway. Using the progressive form ('processing') accurately reflects that the system is actively handling payments at this moment. Options A and B describe states of completion or operational status, while option C incorrectly implies all transactions are finished and D introduces a completely unrelated concept of considering a new process. This nuance is crucial for clear communication during code reviews.
7 / 20
Reviewer: 'I'm seeing that the API endpoint is still returning a 503 error. It seems like you're continuously attempting to call the service. Can you explain what's happening with the retry logic?' Which phrasing best captures the reviewer's concern regarding the ongoing issue?
The question focuses on *aspect* in describing a technical problem. The reviewer is not simply stating that an error exists; they're emphasizing that the system is actively trying to resolve it, repeatedly. Option 3 – 'ongoing' – accurately reflects this continuous action and the resulting errors, while the other options describe static states (unavailable, failed) rather than the dynamic process of retries.
8 / 20
PR Description
Subject: Implement user profile updates.
We've completed the initial development of the user profile update feature. This includes validation logic for new fields and integration with the existing data store. We're currently testing the changes in our staging environment and expect to merge this PR within the next few hours.
The code is now deployed to the staging branch, and we're monitoring its performance closely.
The key here is understanding the difference between simple and perfect tenses. The phrase 'We've completed' indicates a *past* action with a *present* result – the completion itself is still relevant. Option A uses the present continuous incorrectly to describe an ongoing process that's already finished. Options C & D are incorrect because they use the simple past when describing something that has been done and its outcome is still being assessed.
9 / 20
Reviewer: 'I'm seeing that the data ingestion pipeline is still running. It seems like you're continuously collecting logs from multiple sources. Can you elaborate on how frequently the process is triggered and what mechanisms are in place to handle potential failures?' Which of the following best describes the reviewer's intent regarding the log collection activity?
The reviewer uses the term 'continuous' to highlight that the log collection isn't a single event but an ongoing process. Options A and D incorrectly imply a lack of scale or a finished task respectively; these misunderstandings often occur when developers aren't precise with their temporal descriptions. Option C is incorrect because 'perfect' implies completion, which doesn't align with the reviewer's observation. Option B accurately captures the core concern: that the process is ongoing and requires detailed understanding of its timing and error handling.
10 / 20
Reviewer: 'I'm seeing that the payment gateway integration is still running. It seems like you're processing payments in a progressive form. Could you provide more details on the ongoing transaction flow?'
The key here is understanding that 'processing' indicates an action *currently* underway. Using the progressive form ('processing') accurately reflects that the system is actively handling payments at this moment. Options A and B describe states of completion or operational status, while option C incorrectly implies all transactions are finished and D introduces a completely unrelated concept of considering a new process. This nuance is crucial for clear communication during code reviews.
11 / 20
Reviewer: 'I'm seeing that the API endpoint is still returning a 503 error. It seems like you're continuously attempting to call the service. Can you explain what's happening with the retry logic?' Which phrasing best captures the reviewer's concern regarding the ongoing issue?
The question focuses on *aspect* in describing a technical problem. The reviewer is not simply stating that an error exists; they're emphasizing that the system is actively trying to resolve it, repeatedly. Option 3 – 'ongoing' – accurately reflects this continuous action and the resulting errors, while the other options describe static states (unavailable, failed) rather than the dynamic process of retries.
12 / 20
PR Description
Subject: Implement user profile updates.
We've completed the initial development of the user profile update feature. This includes validation logic for new fields and integration with the existing data store. We're currently testing the changes in our staging environment and expect to merge this PR within the next few hours.
The code is now deployed to the staging branch, and we're monitoring its performance closely.
The key here is understanding the difference between simple and perfect tenses. The phrase 'We've completed' indicates a *past* action with a *present* result – the completion itself is still relevant. Option A uses the present continuous incorrectly to describe an ongoing process that's already finished. Options C & D are incorrect because they use the simple past when describing something that has been done and its outcome is still being assessed.
13 / 20
Reviewer: 'I'm seeing that the data ingestion pipeline is still running. It seems like you're continuously collecting logs from multiple sources. Can you elaborate on how frequently the process is triggered and what mechanisms are in place to handle potential failures?' Which of the following best describes the reviewer's intent regarding the log collection activity?
The reviewer uses the term 'continuous' to highlight that the log collection isn't a single event but an ongoing process. Options A and D incorrectly imply a lack of scale or a finished task respectively; these misunderstandings often occur when developers aren't precise with their temporal descriptions. Option C is incorrect because 'perfect' implies completion, which doesn't align with the reviewer's observation. Option B accurately captures the core concern: that the process is ongoing and requires detailed understanding of its timing and error handling.
14 / 20
Reviewer: 'I'm seeing that the payment gateway integration is still running. It seems like you're processing payments in a progressive form. Could you provide more details on the ongoing transaction flow?'
The key here is understanding that 'processing' indicates an action *currently* underway. Using the progressive form ('processing') accurately reflects that the system is actively handling payments at this moment. Options A and B describe states of completion or operational status, while option C incorrectly implies all transactions are finished and D introduces a completely unrelated concept of considering a new process. This nuance is crucial for clear communication during code reviews.
15 / 20
Reviewer: 'I'm seeing that the API endpoint is still returning a 503 error. It seems like you're continuously attempting to call the service. Can you explain what's happening with the retry logic?' Which phrasing best captures the reviewer's concern regarding the ongoing issue?
The question focuses on *aspect* in describing a technical problem. The reviewer is not simply stating that an error exists; they're emphasizing that the system is actively trying to resolve it, repeatedly. Option 3 – 'ongoing' – accurately reflects this continuous action and the resulting errors, while the other options describe static states (unavailable, failed) rather than the dynamic process of retries.
16 / 20
PR Description
Subject: Implement user profile updates.
We've completed the initial development of the user profile update feature. This includes validation logic for new fields and integration with the existing data store. We're currently testing the changes in our staging environment and expect to merge this PR within the next few hours.
The code is now deployed to the staging branch, and we're monitoring its performance closely.
The key here is understanding the difference between simple and perfect tenses. The phrase 'We've completed' indicates a *past* action with a *present* result – the completion itself is still relevant. Option A uses the present continuous incorrectly to describe an ongoing process that's already finished. Options C & D are incorrect because they use the simple past when describing something that has been done and its outcome is still being assessed.
17 / 20
Reviewer: 'I'm seeing that the data ingestion pipeline is still running. It seems like you're continuously collecting logs from multiple sources. Can you elaborate on how frequently the process is triggered and what mechanisms are in place to handle potential failures?' Which of the following best describes the reviewer's intent regarding the log collection activity?
The reviewer uses the term 'continuous' to highlight that the log collection isn't a single event but an ongoing process. Options A and D incorrectly imply a lack of scale or a finished task respectively; these misunderstandings often occur when developers aren't precise with their temporal descriptions. Option C is incorrect because 'perfect' implies completion, which doesn't align with the reviewer's observation. Option B accurately captures the core concern: that the process is ongoing and requires detailed understanding of its timing and error handling.
18 / 20
API Response
HTTP/1.1 200 OKContent-Type: application/json{
"status": "running",
"last_updated": "2024-01-26T10:30:00Z",
"processing_count": 57,
"attempts": 123}
The API response indicates that the process is running continuously. What aspect of this response is most relevant to understanding whether a progressive approach is being used?
The 'attempts' field is key here. A high number of attempts when a process is described as 'running continuously' strongly suggests a progressive approach – repeatedly trying to execute something that isn't immediately succeeding. Option A focuses on the absence of errors (which is related but secondary), while options B, C, and D are less directly relevant to understanding the continuous nature of the processing.
19 / 20
API Response
HTTP/1.1 200 OKContent-Type: application/json{
"status": "running",
"last_updated": "2024-01-26T10:30:00Z",
"processing_count": 57,
"attempts": 123}
The API response indicates that the process is running continuously. What aspect of this response is most relevant to understanding whether a progressive approach is being used?
The 'attempts' field is key here. A high number of attempts when a process is described as 'running continuously' strongly suggests a progressive approach – repeatedly trying to execute something that isn't immediately succeeding. Option A focuses on the absence of errors (which is related but secondary), while options B, C, and D are less directly relevant to understanding the continuous nature of the processing.
20 / 20
In a code review comment, you see: 'The API endpoint is continuously processing requests. It appears to be operating in a progressive fashion.' What aspect of the API's behavior is being highlighted?
'Progressive' here indicates continuous operation. The API isn't handling one request at a time; it's processing multiple requests without interruption. Options 1 and 3 describe limitations on concurrency, while option 4 describes scheduled behavior.
What will I practise in "Aspect in Technical English: Simple vs Progressive vs Perfect | CoderSlingo"?
Practise choosing the right verb aspect in standups, release notes, and Slack messages. 5 interactive grammar exercises.
How many exercises are in this module?
This module has 20 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.