5 exercises — practise stop, remember, and regret with gerunds and infinitives that change meaning in dev scenarios.
0 / 6 completed
1 / 6
Which sentence means the engineer halted an ongoing action (logging)?
"The service stopped logging every request after the config change" is correct: "stop + gerund" means to cease an ongoing activity, exactly the meaning intended here — logging was happening and then it ceased. Option B, "stopped to log", means the service paused in order to log (log was the purpose of stopping), the opposite, unintended meaning. Option C changes the tense inconsistently and adds an unrelated infinitive of purpose, distorting the sentence. Option D is missing the required "-ing" or "to" form entirely, producing an ungrammatical verb sequence.
2 / 6
Which sentence means the engineer paused a task in order to perform a different action?
"She stopped to check the dashboard before continuing the deployment" is correct: "stop + infinitive" means pausing one activity in order to do something else, here pausing the deployment work to check the dashboard. Option B, "stopped checking", would mean she used to check the dashboard and ceased that habit entirely, a different meaning than a brief pause for a specific check. Option C uses an ungrammatical bare infinitive after "stops". Option D incorrectly uses a past-tense form "checked" after "stopped", which is not a valid verb pattern.
3 / 6
Which sentence correctly expresses that the engineer recalls a past action (already having deployed) using "remember"?
"I remember deploying that hotfix last Friday" is correct: "remember + gerund" refers to recalling a past event that already happened, matching the intended meaning of a memory of a completed deployment. Option B, "remember to deploy", would mean recalling a future obligation not yet completed, the opposite meaning. Option C uses an ungrammatical bare infinitive after "remembered". Option D uses an unnatural present continuous form of "remember", which is not typically used this way since "remember" is a stative verb.
4 / 6
Which sentence correctly expresses a reminder about a future obligation using "remember"?
"Please remember to revoke the temporary access key after the migration" is correct: "remember + infinitive" refers to not forgetting to do a future action, exactly the intended meaning of a reminder for a task not yet done. Option B, "remember revoking", would incorrectly imply recalling a past act of revoking the key, not a future reminder. Option C uses an ungrammatical bare infinitive after "remember". Option D incorrectly uses the past tense "remembered" in an imperative sentence, which is ungrammatical.
5 / 6
Which sentence correctly expresses regret about a past action using "regret" plus a gerund?
"We regret merging that pull request without a second review" is correct: "regret + gerund" expresses sorrow about a past action already taken, matching the meaning that the merge already happened and is now regretted. Option B, "regret to merge", uses the formal "regret + infinitive" pattern reserved for announcing bad news about a present or future action (as in "we regret to inform you"), not for expressing remorse about a completed past act, so it does not fit this context. Option C uses an ungrammatical bare infinitive after "regret". Option D mixes "regretted" with "to merging", an invalid, doubled construction.
6 / 6
Chloe (in a code review comment): 'I regret that we didn't implement proper error handling earlier.'
Which phrase accurately conveys Chloe's feeling?
When expressing regret about a past action (something that *didn't* happen), we use 'regret' followed by the gerund form of the verb. The infinitive would suggest an intention to do something differently in the future, which is not what Chloe means here. This is a classic example where the gerund correctly expresses remorse for a missed opportunity.
What will I practise in "Verbs Where Gerund vs Infinitive Changes Meaning — IT Grammar Exercise"?
Practise stop, remember, and regret followed by a gerund versus an infinitive, where the choice changes the meaning, in developer scenarios like deployments
How many exercises are in this module?
This module has 6 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.