Review: Action Object vs Goal

By the end of this lesson, you will be able to...

• Classify a second action as an action object or a goal in short engineering sentences.

• Choose between doing and to do when rewriting PR comments, status updates, and planning notes.

• Explain why a sentence changes meaning when the pattern changes.

Idea in one sentence: Use doing when the second action is the thing under discussion, and use to do when the second action is the goal, next step, requirement, plan, or decision.

Core Insight

The first four lessons gave you two useful shapes.

Shape one:

doing = the action is the object of the sentence

Examples:

We discussed splitting the table.
We avoided dropping events.
We stopped retrying the job.

Shape two:

to do = the action is a goal, next step, need, plan, or decision

Examples:

We agreed to split the table.
We need to update the schema.
We decided to roll back.

This review lesson is about choosing under mixed pressure. Real technical writing rarely gives you one grammar pattern at a time. A pull request comment may mention a thing you discussed, a thing you avoided, a thing you need, and a thing you decided.

The useful question is not "What is the grammar label?"

The useful question is:

What job does the second action have in this sentence?

If the second action is the thing you discuss, avoid, finish, keep, or stop, use doing.

If the second action is the goal you agree, need, want, plan, or decide, use to do.

The Small Situation

Imagine a team working on a migration from a large events table to two smaller tables.

They have a PR, a rollout note, and an incident channel open at the same time. The team needs to write short English that a reviewer can scan quickly.

One engineer writes this mixed note:

We discussed to split the table, but we decided keeping the old index for one week. We need updating the schema before deploy, and we stopped to retry the failed jobs.

The reader can guess the meaning, but the note has four pattern problems.

The better version is:

We discussed splitting the table, but we decided to keep the old index for one week. We need to update the schema before deploy, and we stopped retrying the failed jobs.

Now each second action has a visible job.

That table is the review tool. Do not start by asking which verb is on a memorized list. Start by asking what role the second action plays.

The Naive Rule

A naive rule is:

If the action is technical, use the same form everywhere.

That rule breaks immediately.

Compare these two sentences:

We stopped retrying the job.
We stopped to retry the job.

The first sentence means the retries ended. That is common in incident notes:

We stopped retrying the job because duplicate writes were increasing.

The second sentence means the team stopped another activity in order to retry the job. That is possible English, but it says something else:

We stopped the deploy to retry the job manually.

Small pattern, different meaning.

The same problem appears with discuss.

Natural:

We discussed splitting the table.

Unnatural:

We discussed to split the table.

Discuss treats the second action as the topic of discussion. The action is the object, so use doing.

But agree points to a chosen future action:

We agreed to split the table.

Agree splitting the table is not the natural engineering sentence.

A Worked Rewrite

Use this rough note as input:

We finished to backfill the new table. We plan running the migration tomorrow. We avoided to change the API response. We want reducing manual review before release.

Step one: mark the first verb.

Step two: choose the pattern by meaning.

Step three: rewrite the note.

We finished backfilling the new table. We plan to run the migration tomorrow. We avoided changing the API response. We want to reduce manual review before release.

Input:

literal or mixed second-action patterns

Transition:

for each first verb, decide the job of the second action

Intermediate state:

finish/avoid -> action object -> doing
plan/want -> goal -> to do

Output:

a note where each action has a visible role

Naive failure contrast:

same technical nouns, but wrong action role

That is the whole review skill.

Action Object or Goal

Here is a compact decision test.

Ask:

Can I point to the second action as the thing being discussed, avoided, finished, kept, or stopped?

If yes, doing is likely:

We discussed splitting the table.
We avoided changing the API response.
We finished backfilling the new table.
We kept monitoring the queue.
We stopped retrying the job.

Ask:

Is the second action a goal, requirement, plan, desire, decision, or agreed next step?

If yes, to do is likely:

We agreed to split the table.
We need to update the schema.
We plan to run the migration.
We want to reduce manual review.
We decided to keep the old index.

This is not every verb pattern in English. It is the core contrast this first cluster needs.

Trade-offs and Limits

The action object vs goal test is useful because it is fast. You can use it while writing a PR comment or a deployment note.

The trade-off is speed versus coverage. The test helps you choose quickly in many common sentences, but it does not cover every verb pattern in English.

It also has a cost: you must look at meaning, not only the first verb. Some verbs have special patterns. Some verbs change meaning depending on the pattern. Lesson 006 starts there with try doing versus try to do.

The test also does not replace a dictionary or grammar reference. If a sentence sounds strange after the meaning is clear, check the verb pattern.

You can see the boundary when both sentences are grammatical but mean different things:

We stopped retrying the job.
We stopped to retry the job.

At that boundary, grammar is not decoration. Grammar changes the technical story.

Common Confusions

Confusion: Every Future Action Uses to

Why it is tempting:

Many to do sentences point forward:

We need to update the schema.

Better model:

Future meaning is not enough. If the second action is the object of a verb like avoid, finish, or discuss, use doing:

We avoided changing the API before release.

Confusion: Every Technical Process Uses doing

Why it is tempting:

Technical work often sounds like an activity: migrating, backfilling, deploying, monitoring.

Better model:

The same technical action can be a goal:

We plan to migrate tomorrow.

Or it can be the action object:

We discussed migrating tomorrow.

The noun is not the decision. The action's job is the decision.

Check Your Understanding

Check: Which sentence means the team chose a future action?

A. We decided keeping the old index for one week.
B. We decided to keep the old index for one week.

Think first, then reveal.

Answer: B. Decided to keep says the team chose a future action. Decided keeping is not the natural pattern.

Check: Which sentence says the retries ended?

A. We stopped retrying the job.
B. We stopped to retry the job.

Think first, then reveal.

Answer: A. Stopped retrying says the retry action ended. Stopped to retry means the team stopped something else in order to retry.

Practice

Rewrite each rough sentence. Then name the role of the second action: action object or goal.

1. We discussed to add a retry limit.
2. We need adding a rollback check.
3. We avoided to change the public API.
4. We plan running the migration after the backfill.

Model answer:

1. We discussed adding a retry limit. The second action is the topic, so it is an action object.
2. We need to add a rollback check. The second action is required, so it is a goal.
3. We avoided changing the public API. The second action is the avoided action, so it is an action object.
4. We plan to run the migration after the backfill. The second action is an intended future step, so it is a goal.

Daily Practice Lines

Repeat these during the day:

We discussed splitting the table.
We need to update the schema.
We stopped retrying and decided to roll back.

Then change one noun:

table -> queue -> cache -> parser -> migration

Keep the practice small. The goal is not to recite grammar. The goal is to make the sentence shape available when you need it.

Resources

• [ARTICLE] Cambridge Dictionary Grammar: Verb patterns - Use this to check common verb patterns after you decide the sentence meaning.
• [ARTICLE] Cambridge Dictionary Grammar: Infinitives - Use this as a reference for to do forms and purpose-like meanings.
• [ARTICLE] Microsoft Writing Style Guide - Use this for short, reader-friendly technical sentences.

Key Takeaways

• Use doing when the second action is the thing discussed, avoided, finished, kept, or stopped.
• Use to do when the second action is a goal, requirement, plan, desire, decision, or agreed next step.
• Do not choose the pattern from the technical noun alone. Choose it from the job the second action has in the sentence.
• Some pairs are grammatically possible but mean different things. That is the bridge into try doing versus try to do.