Worth Doing and No Point In Doing

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

• Evaluate an engineering action with be worth doing.

• Explain that an action has little or no useful value with there is no point in doing.

• Keep evaluation separate from a plan, an obligation, and a measured result.

Idea in one sentence: Worth doing says that an action's value justifies its cost, while no point in doing says that the action is unlikely to help in the current situation.

Core Insight

A team is reviewing a proposed cleanup before a production migration. Someone suggests rewriting the whole retry module. Another engineer asks a smaller question:

Is it worth rewriting the retry module before the migration?

The team may answer:

It is worth testing the rollback path first.
There is no point in rewriting the retry module before we understand the failure.

These sentences do not merely describe what the team will do. They evaluate whether an action deserves time, risk, and attention. That makes them useful in design reviews, pull request comments, incident follow-ups, and implementation plans.

The activity after worth or in is treated like a noun:

worth testing
no point in rewriting

The writer is talking about the value or usefulness of the activity itself. The sentence is not saying that the activity is happening now. It is judging whether doing it makes sense.

The Confusion This Concept Solves

The tempting translation is:

It is worth to test the rollback.
There is no point to rewrite the retry module.

The patterns are not natural in standard technical English. Use worth + -ing and point in + -ing:

It is worth testing the rollback.
There is no point in rewriting the retry module.

This is another place where to + verb is not the default answer. Earlier lessons used to for plans, decisions, needs, and direct purpose:

We plan to test the rollback.
We added a dashboard to monitor the rollback signal.

Those sentences describe an intended action. It is worth testing the rollback evaluates the action. The team may decide to test it because it is worth doing, but evaluation and decision are separate steps.

A Small Example

The team has one hour before a staging window closes. It has three possible actions:

1. inspect the rollback path;
2. rename every variable in the worker;
3. add a dashboard for query latency.

The review note says:

It is worth inspecting the rollback path before the window closes.
There is no point in renaming every variable before the behavior is stable.
The dashboard is worth adding if the team will use it during the migration.

The first action has high immediate value because it reduces uncertainty around a risky operation. The second may be useful later, but its value is low in this time window. The third depends on a condition: a dashboard is worth adding when it will support a real decision, not simply because more monitoring sounds good.

Worth doing does not mean “easy” or “certain to succeed.” An action can be difficult and still be worth doing. No point in doing does not mean “the action is always useless.” It means that the action has no useful purpose under the current constraints or with the current information.

The Precise Meaning

It is worth doing: value justifies cost

Use this pattern when the expected benefit justifies the time, effort, risk, or attention:

It is worth testing the rollback path.
It is worth checking the query plan before adding another index.
It is worth keeping the old parser during the first rollout.

The activity after worth uses -ing. The subject it is a general placeholder for the situation or action:

Is it worth migrating the table now?
It is not worth changing the schema during the incident.
Was it worth adding the extra validation step?

You can also put a noun after worth:

The rollback test is worth the extra hour.
The migration is worth the risk only with a tested restore.

When you name the activity directly, use worth doing, not worth to do:

The rollback is worth testing.

The activity can include an object or condition:

It is worth testing the rollback in staging before changing production.

There is no point in doing: no useful benefit here

Use this pattern when an action would consume effort without improving the current decision or outcome:

There is no point in restarting the worker before fixing the configuration.
There is no point in collecting more logs if the request ID is missing everywhere.
There is no point in optimizing the query before confirming that it is the bottleneck.

The action follows the preposition in, so use a noun or -ing activity:

There is no point in another restart.
There is no point in restarting the worker again.

This pattern is often a polite way to reject an action. It is better than simply saying “do not do it” when the reason is wasted effort:

There is no point in adding another alert if nobody will own the response.

The sentence does not necessarily criticize the person who proposed the action. It explains why the action does not fit the current goal or evidence.

What This Is Not

Not a plan

Compare:

It is worth testing the rollback.
We plan to test the rollback tomorrow.

The first is a judgment about value. The second is a commitment about the future. They can appear together:

It is worth testing the rollback, so we plan to run it tomorrow.

Not an obligation

Should or need to expresses a stronger requirement:

We need to test the rollback before production.

Worth testing says that the action has enough value. It does not, by itself, assign responsibility or set a deadline.

Not a result

It was worth testing the rollback is an evaluation after the action, but it still does not give the evidence. Add the reason:

It was worth testing the rollback because the test revealed a missing database restore step.

The discovery explains why the effort was valuable. Without that evidence, “worth it” can be a reasonable judgment, but it is less inspectable.

A Worked Design Review

Let us trace one proposal. The input is a worker that retries failed jobs too aggressively. The team has limited time and must choose a next step.

The sequence is:

symptom -> evaluate action -> reject wasted action -> gather evidence -> choose plan

The grammar helps the note show the difference between a judgment and a commitment. It does not make the engineering decision automatically. The team still needs a useful signal and a constraint such as time, risk, or ownership.

Common Confusions

Confusion: worth to do

After worth, use a noun or -ing activity:

It is worth checking the logs.
The check is worth the time.

Do not write It is worth to check the logs in this pattern. If you want to + verb, change the structure:

We plan to check the logs.

Confusion: no point to do

After point in this expression, use in + noun/-ing:

There is no point in changing the timeout before checking the evidence.

The word point can appear in other meanings, so do not generalize the pattern to every sentence containing point. Here it means useful purpose or benefit.

Confusion: worth doing means easy

An action can be expensive and still be worth doing:

It is worth rebuilding the index during the maintenance window.

The phrase evaluates value against cost. It does not say that the action is quick.

Confusion: no point in doing means impossible

An action may be possible but still not useful now:

There is no point in adding another dashboard if the team will not use it.

The dashboard can be built. The problem is that it does not improve the current workflow without an owner or decision attached to it.

Worked Classification

Classify each sentence before looking at the explanation.

Check: The team has one hour and needs to know whether rollback works.

Think first, then reveal.

Answer: It is worth testing the rollback path. The sentence evaluates the action as valuable under the time constraint. It does not yet say who will test it or exactly when.

Check: The team has already confirmed that the alert is not connected to the failing worker.

Think first, then reveal.

Answer: There is no point in tuning that alert during this investigation. The action is possible, but it will not improve the current diagnosis.

Check: The team accepted the evaluation and assigned a next step.

Think first, then reveal.

Answer: We plan to test the rollback in staging. This is a plan, not just an evaluation. The team has moved from “worth doing” to a concrete commitment.

Practice

Rewrite each sentence for the meaning in parentheses.

1. The rollback test has enough value to justify the time. (evaluation)
2. Rewriting the worker now will not help until the retry condition is known. (no useful purpose)
3. The team has accepted the proposal and will run the test tomorrow. (plan)
4. The team wants to evaluate whether another dashboard is useful before building it. (question)

Model answers:

1. It is worth testing the rollback.
2. There is no point in rewriting the worker before we understand the retry condition.
3. The team plans to run the test tomorrow.
4. Is it worth adding another dashboard?

Now write a short design-review comment about one technical action. Use two sentences:

It is worth [doing something] because [benefit or evidence].
There is no point in [doing something else] until [condition].

Use a service, worker, queue, cache, migration, or alert as the object. A strong answer makes the cost or constraint visible. For example:

It is worth testing the restore because the migration changes user data. There is no point in tuning the cache until we confirm that the database query is the bottleneck.

Daily Practice Lines

Repeat these during the day. The third line revisits the purpose pattern from lesson 010.

• It is worth testing the rollback.
• There is no point in changing the schema during the incident.
• We added a dashboard to monitor queue latency.

Change one technical noun when the pattern feels easy: rollback, schema, worker, cache, migration, or alert. Keep worth followed by -ing, and keep in before the activity in no point in doing.

Trade-offs and Limits

These patterns make evaluation concise. They let a writer reject wasted work without issuing a bare command, and they let a design review explain why a small test deserves attention. The trade-off is that worth always compares value with a cost, even when the cost is not written. A reader may ask “worth the time, risk, or complexity?” if the context does not answer that question.

The patterns do not prove that an action will succeed or that everyone will agree with the evaluation. “Worth doing” is a judgment based on the evidence available now. New evidence can change it:

It was worth testing the rollback, but the result showed that the restore path is incomplete.

The test was valuable because it exposed a problem, even though it did not produce a successful rollback. Likewise, “no point in doing” is local to a goal and situation. There may be a point later, after the missing condition changes.

Resources

• [ARTICLE] Cambridge Dictionary: Worth - Review worth + noun and worth + -ing, including questions and negative evaluations.
• [ARTICLE] Cambridge Dictionary: Point - Check the meaning of there is no point in doing something as a lack of useful purpose.
• [ARTICLE] Microsoft Writing Style Guide - Make design-review judgments concrete by naming the action, the cost, and the evidence behind the recommendation.

Key Takeaways

• Use It is worth doing to say that an action's value justifies its cost: It is worth testing the rollback.
• Use There is no point in doing to say that an action is not useful in the current situation: There is no point in rewriting the worker yet.
• After worth and in in these patterns, use a noun or -ing, not to + verb.
• Worth doing is an evaluation; plan to do is a commitment; need to do is an obligation.
• The judgment can change when new evidence, costs, or constraints appear.