Try Doing vs Try To Do

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

• Explain the difference between try doing and try to do in technical suggestions.

• Choose the pattern that matches an experiment, an attempt, or a failed attempt.

• Rewrite debugging notes so the reader can see whether you mean "test this change" or "attempt this goal."

Idea in one sentence: Use try doing for an experiment you test, and use try to do for an attempt to achieve a goal.

Core Insight

Lesson 005 gave you a useful test:

doing = the action is the thing under discussion
to do = the action is a goal or next step

Try is the first verb in this track that makes that test more interesting.

Both of these sentences are grammatical:

Try increasing the timeout before changing the client.
Try to increase the timeout before changing the client.

They do not mean the same thing.

Try increasing the timeout means:

Test this change and see whether it helps.

Try to increase the timeout means:

Make an effort to increase the timeout.

The first sentence treats increasing the timeout as an experiment. The second treats increasing the timeout as a goal that may be difficult.

That difference matters in engineering work. Debugging often needs experiments. Operations often need attempts. The grammar tells the reader which one you mean.

The Small Situation

A service is timing out when it calls a slow search API.

The team sees this in the logs:

search_api timeout after 200ms
retry count: 3
user-visible error rate: 4%

One engineer writes in chat:

Try increasing the timeout to 500ms before changing the client.

This is a debugging suggestion. The engineer is not saying, "The hard goal is to increase the timeout." The engineer is saying, "Test this small change and observe the result."

Now imagine a different message:

I tried to increase the timeout, but the gateway rejects values above 300ms.

This is not a suggestion. It is a report about an attempted action. The engineer had a goal: increase the timeout. The system blocked that goal.

Same first verb. Different pattern. Different technical meaning.

The Naive Idea

The naive idea is:

After try, either pattern is fine.

It is tempting because both patterns can sound close in Spanish. It is also tempting because both patterns can appear near the same technical noun:

timeout
client
cache
parser
retry limit

But the pattern changes the reader's mental model.

Compare:

Try clearing the cache.
Try to clear the cache.

Try clearing the cache means clearing the cache is an experiment. Maybe it helps; maybe it does not.

Try to clear the cache means clearing the cache is the goal. Maybe you do not have permission, or the command fails, or the cache service is unavailable.

The technical noun is the same. The role of the action is different.

The Precise Meaning

Plain meaning:

Try doing means "test this action as a possible way to learn or improve something."

In this scenario:

The team can increase the timeout and watch whether user-visible errors go down.

Technical name:

This is an experiment pattern.

Plain meaning:

Try to do means "make an effort to complete this action."

In this scenario:

An engineer may attempt to increase the timeout, but a gateway rule may block the change.

Technical name:

This is an attempt pattern.

You do not need the grammar labels in daily work. The labels are useful only because they help you choose the sentence.

A Worked Debugging Thread

Here is a short debugging thread.

Input:

The search API is slow. The client retries too quickly. Users see errors.

The team has two possible comments:

A. Try increasing the timeout to 500ms before changing the client.
B. Try to increase the timeout to 500ms before changing the client.

Step one: ask what the writer wants the reader to understand.

Step two: choose the experiment pattern.

Try increasing the timeout to 500ms before changing the client.

Intermediate state:

increase timeout -> deploy config -> watch error rate -> decide next step

Output if the experiment helps:

Increasing the timeout reduced search errors from 4% to 1%.

Output if it does not help:

Increasing the timeout did not reduce errors, so the client retry behavior is still suspicious.

Naive failure contrast:

Try to increase the timeout to 500ms.

That sentence makes the reader expect an obstacle to the action itself. It is not wrong if the action is difficult. It is less precise if the real message is "run this experiment."

Now change the situation.

Input:

The gateway has a hard 300ms timeout limit. The team wants 500ms.

Better sentence:

We tried to increase the timeout to 500ms, but the gateway rejected the value.

Here the goal was not completed. Tried to increase fits because the sentence reports an attempted goal and the obstacle that blocked it.

What This Changes

Before this distinction, a debugging note can sound vague:

Try to increase the timeout.

The reader may ask:

Are you suggesting an experiment?
Or are you saying the timeout change is difficult?

After this distinction, the sentence tells the reader what kind of work comes next.

Use try doing when you want a small experiment:

Try disabling the cache for one request.
Try lowering the batch size.
Try logging the parser input before normalization.

Use try to do when you want to describe effort toward a goal:

We tried to disable the cache, but the flag is not available in staging.
We tried to lower the batch size, but the job still exceeded memory.
We tried to log the parser input, but the payload contains secrets.

The action after try is not only an action. It tells the reader whether to expect evidence or an obstacle.

A Small Meaning Map

When you are unsure, look at the words after the phrase with try.

Experiment sentences often include an observation:

Try increasing the timeout and watch the error rate.
Try lowering the batch size and check memory usage.
Try disabling the cache for one request and compare latency.

The second half says what evidence to inspect. That is a strong signal for try doing.

Attempt sentences often include a blocker, success, or failure:

We tried to increase the timeout, but the gateway rejected it.
We tried to lower the batch size, but the job config is read-only.
We tried to disable the cache, but staging does not have the flag.

The second half says what happened to the goal. That is a strong signal for try to do.

Here is the same action in both roles:

This map is not a new rule to memorize. It is a reading habit.

If the sentence is asking for evidence, choose the experiment pattern.

If the sentence is reporting whether the action could be completed, choose the attempt pattern.

So far, the important move is this:

experiment -> try doing -> look for evidence
attempted goal -> try to do -> look for success, failure, or blockage

That small map helps when you write quickly in Slack, a PR comment, or an incident note. You do not need to stop and name the grammar. You only need to ask what the reader should expect after the action: a measurement, or an obstacle.

That expectation is the meaning of the pattern.

It guides the next sentence.

Trade-offs and Limits

The trade-off is precision versus simplicity.

Try doing is precise for experiments, but it asks the writer to think about the purpose of the action. Is the action itself the test? Or is the action a difficult goal?

Try to do is precise for attempted goals, but it can sound like the action may fail. If the action is easy and the point is to observe the result, try to do adds the wrong pressure.

This distinction does not solve every sentence with try. Some sentences are ambiguous without context:

Try restarting the worker.

This usually means "restart it and see whether that helps." But if the worker is stuck and the command may fail, a report might say:

We tried to restart the worker, but the process manager was down.

You can see the boundary when the sentence needs the next clause:

Try increasing the timeout and watch the error rate.
We tried to increase the timeout, but the gateway rejected it.

The signal is the follow-up. Experiments usually lead to observations. Attempts often lead to success, failure, or obstacles.

Common Confusions

Confusion: Try To Do Is Always More Formal

Why it is tempting:

To do often feels more formal to learners because it appeared in planning language: need to, plan to, decide to.

Better model:

Formality is not the main difference. Meaning is the difference.

Try increasing the timeout.

is normal, clear technical English when the timeout change is an experiment.

Confusion: Try Doing Means The Action Is Casual

Why it is tempting:

Experiments can sound informal, especially in chat.

Better model:

Try doing can be serious. It says the action is a test, not that the problem is unimportant.

Try disabling writes on the secondary before restarting replication.

That is a serious operational suggestion. The pattern still means "test this action as a way to learn or improve the situation."

Confusion: The Technical Verb Decides The Pattern

Why it is tempting:

Some actions feel like operations: restarting, increasing, disabling, logging.

Better model:

The same action can be an experiment or an attempted goal.

Try logging the parser input.
We tried to log the parser input, but the payload contains secrets.

The verb log did not decide the pattern. The sentence meaning did.

Check Your Understanding

Check: You want to suggest a small experiment during debugging. Which sentence fits better?

A. Try increasing the timeout and watch the error rate.
B. Try to increase the timeout and watch the error rate.

Think first, then reveal.

Answer: A. Try increasing treats the timeout change as an experiment. The phrase watch the error rate confirms that the writer expects evidence.

Check: You attempted a change, but a system rule blocked it. Which sentence fits better?

A. We tried increasing the timeout, but the gateway rejected the value.
B. We tried to increase the timeout, but the gateway rejected the value.

Think first, then reveal.

Answer: B. Tried to increase reports an attempted goal. The gateway rejection is the obstacle.

Practice

Choose try doing or try to do. Then explain your choice in one sentence.

1. Suggest an experiment: lower the batch size and see whether memory drops.
2. Report a failed attempt: lower the batch size, but the job config is read-only.
3. Suggest an experiment: disable the cache for one request and compare latency.
4. Report an attempt: disable the cache, but the feature flag is missing.

Model answer:

1. Try lowering the batch size and watch memory usage. This is an experiment.
2. We tried to lower the batch size, but the job config is read-only. This is an attempted goal with an obstacle.
3. Try disabling the cache for one request and compare latency. This is an experiment.
4. We tried to disable the cache, but the feature flag is missing. This is an attempted goal with an obstacle.

Daily Practice Lines

Repeat these during the day:

Try increasing the timeout before changing the client.
We tried to increase the timeout, but the gateway rejected it.
We stopped retrying and decided to roll back.

Then change one technical noun:

timeout -> batch size -> cache -> parser input -> retry limit

Keep the contrast visible: experiment first, attempted goal second.

Connections

This lesson extends the review in lesson 005. Try doing treats the action as the thing you test. Try to do points toward a goal.

It also prepares lesson 007. Remember doing and remember to do will use a similar idea: the pattern changes the time and responsibility of the action.

Resources

• [ARTICLE] Cambridge Dictionary Grammar: Verb patterns - Use this to compare verbs that can take doing or to do with different meanings.
• [ARTICLE] Cambridge Dictionary Grammar: Infinitives - Use this as a reference for to do patterns when the action is a goal or attempt.
• [ARTICLE] Microsoft Writing Style Guide - Use this for clear, direct technical suggestions and status notes.

Key Takeaways

• Use try doing when the action is an experiment: test it and observe what changes.
• Use try to do when the action is an attempted goal: the sentence often mentions success, failure, or an obstacle.
• The technical verb does not decide the pattern. The action's job in the sentence decides it.
• Follow-up words help: experiments lead to evidence; attempted goals lead to completion or blockage.