Too Risky To Do and Safe Enough To Ship

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

• Use too + adjective + to + verb to say that a condition blocks an action.

• Use adjective + enough + to + verb to say that a condition meets the threshold for an action.

• Describe release readiness without turning “safe enough” into a guarantee of safety.

Idea in one sentence: Too risky to ship places a change beyond the acceptable boundary, while safe enough to ship says that the available evidence meets the current release threshold.

Core Insight

A team is deciding whether to release a new queue worker. The worker passes unit tests, but the rollback path has not been exercised under load. The release note needs to express a judgment, not just list facts:

The change is too risky to ship today.
The canary is safe enough to ship to five percent of traffic.

These sentences use the same basic shape: an adjective describes the subject, and to + verb names the action being judged. The difference is the boundary:

• too risky to ship says the risk is beyond what the team accepts for this action;
• safe enough to ship says the change has reached the minimum level required for this limited action.

The second sentence does not say that the worker is perfectly safe. Five percent of traffic is a smaller exposure, and the team may still need to watch error rate and rollback time. “Enough” is always enough for a stated decision, under stated conditions.

The Small Situation

The payments team has prepared a worker change. It has three possible release stages:

1. keep the change in staging;
2. send it to a small canary group;
3. release it to all traffic.

The first draft of the decision note says:

The change has too risk to deploy.
The canary has safety enough to ship.

The writer has translated the adjective as a noun and placed enough in the wrong position. The repaired note says:

The change is too risky to deploy to all traffic.
The canary is safe enough to ship to five percent of traffic.

The patterns are:

The to + verb phrase shows the action that the degree enables or blocks. Too risky to ship is not simply “very risky.” It connects the risk level to a specific action.

The Naive Idea

The tempting rule is:

Put enough before the adjective, as in enough safe.

That creates:

The canary is enough safe to ship.

With an adjective, enough comes after the adjective:

The canary is safe enough to ship.

But enough comes before a noun:

We have enough evidence to proceed.
We have enough rollback capacity to limit the exposure.

The second tempting rule is:

Use too whenever an adjective is strong.

Too risky to ship does not mean merely “very risky.” It means the risk prevents the specified action under the current standard. Compare:

The change is very risky, but the team may still run it in a small canary.
The change is too risky to ship to all traffic today.

The first describes degree. The second makes a decision boundary visible.

The Two Boundaries

Too risky to do: the condition blocks the action

Use too + adjective + to + verb when the degree is more than the current action can accept:

The migration is too large to run during the short maintenance window.
The rollback signal is too weak to support a full release.
The worker is too unstable to receive production traffic.
The evidence is too incomplete to approve the change.

The sentence often implies a consequence or a different plan:

The change is too risky to ship today, so we will keep it in staging.

The blocked action matters. A change may be too risky to ship to all traffic but not too risky to test in staging. Add the boundary when the release scope matters:

The change is too risky to ship globally, but it is safe enough to test with synthetic traffic.

Safe enough to do: the condition meets a threshold

Use adjective + enough + to + verb when the degree is sufficient for the specified action:

The canary is stable enough to receive five percent of traffic.
The rollback signal is clear enough to support the next step.
The migration is small enough to run during the maintenance window.
The evidence is strong enough to approve a limited rollout.

“Enough” does not mean perfect. It means sufficient for a goal, risk level, audience, or scope. A canary can be safe enough for five percent of traffic but not safe enough for a global release.

The phrase can be negative:

The rollback signal is not clear enough to support a full release.

This is often more precise than too unclear, because it identifies the missing threshold. The team can ask what evidence would make the signal clear enough.

A Worked Release Decision

Let us trace the worker from test result to release decision. The input is a canary with a stable error rate but an untested rollback path.

The path is:

evidence -> boundary judgment -> limited action -> new evidence -> wider decision

The grammar makes the boundary concise, but the numbers and signals make it credible. A release note should say what “enough” means when the decision has real consequences:

The canary is stable enough to expand because error rate stayed below 0.5% for thirty minutes and rollback completed in under two minutes.

What This Changes in Engineering Communication

These patterns help a writer avoid both reckless confidence and vague hesitation. Compare:

The change is risky.
The change is too risky to ship globally today.
The change is safe enough to test with five percent of traffic.

The first is a general observation. The second links risk to a blocked action. The third links evidence to an allowed scope. A reviewer can respond to the boundary:

What would make the change safe enough to ship globally?

The answer should name a signal, not just repeat the adjective:

We need a faster rollback and thirty minutes of stable error rate before a global release.

The pattern also helps separate a release judgment from a recommendation:

The change is too risky to ship today.
We should keep it in staging and test the rollback.

The first states the boundary. The second states the next action. The team can use both in a short pull request or rollout note.

Common Confusions

Confusion: enough safe

With an adjective, put enough after it:

The build is stable enough to deploy.

With a noun, put enough before it:

We have enough evidence to deploy.

Confusion: too risky means impossible in every context

The action after to defines the boundary:

The change is too risky to ship globally.
The change is safe enough to test in staging.

There is no contradiction. The same change can be unacceptable for a large exposure and acceptable for a small, reversible experiment.

Confusion: safe enough is a guarantee

Safe enough to ship is a threshold judgment, not a promise that nothing will fail. Add scope and evidence:

The canary is safe enough to expand to ten percent, but the team will keep the rollback button ready.

Confusion: too and very mean the same thing

Very risky describes intensity. Too risky to ship says that intensity crosses a boundary for a particular action. Use too when the consequence matters.

Check Your Understanding

Check: The team has stable error rates for five percent of traffic, but global rollback is still slow. Which sentence is precise?

Think first, then reveal.

Answer: The canary is safe enough to serve five percent of traffic, but the rollback is too slow to support a global release. Each adjective is evaluated against a different action and scope.

Check: The writer wants to say that evidence is sufficient for a limited approval. Which sentence fits?

Think first, then reveal.

Answer: We have enough evidence to approve the limited rollout. Enough comes before the noun evidence. Another natural sentence is The evidence is strong enough to approve the limited rollout.

Check: The team can test the change but should not release it globally. Which sentence avoids overclaiming?

Think first, then reveal.

Answer: The change is too risky to ship globally, but it is safe enough to test in staging. The two actions have different thresholds.

Practice

Rewrite each sentence for the meaning in parentheses.

1. The change exceeds the acceptable risk for a global release today. (blocked action)
2. The canary meets the minimum stability threshold for ten percent of traffic. (allowed action)
3. The evidence quantity is sufficient to approve a limited rollout. (enough + noun)
4. The rollback signal does not meet the clarity threshold for a full release. (negative threshold)

Model answers:

1. The change is too risky to ship globally today.
2. The canary is stable enough to receive ten percent of traffic.
3. We have enough evidence to approve a limited rollout.
4. The rollback signal is not clear enough to support a full release.

Now write a short release decision with two sentences:

The change is too [adjective] to [action] because [evidence or missing condition].
It is [adjective] enough to [smaller or safer action] if [scope or signal].

For example:

The migration is too large to run during the ten-minute window because rollback has not been measured. It is small enough to test in staging if the team captures the restore time.

Use a service, worker, queue, cache, migration, or alert. Make the action after to visible; “safe enough” is incomplete without saying safe enough for what.

Daily Practice Lines

Repeat these during the day. The third line revisits the evaluation pattern from lesson 012.

• The change is too risky to deploy globally.
• The canary is stable enough to expand.
• It is worth testing the rollback.

Change the adjective or object when the lines feel easy: too large, too slow, clear enough, safe enough, migration, worker, queue, or alert. Keep enough after adjectives and before nouns.

Trade-offs and Limits

These patterns make release judgments compact and actionable. They help a reader see which action is blocked, which action is allowed, and what threshold the team is discussing. The trade-off is that the writer must name or imply a boundary. Without scope, safe enough can sound like a broad guarantee, and too risky can sound more absolute than intended.

The grammar does not calculate risk or define the right threshold. A change can be safe enough for a canary and too risky for a global release. It can also be judged safe enough based on incomplete evidence and fail later. Pair the sentence with exposure, time, rollback, error rate, or another observable signal:

The canary is safe enough to expand to ten percent because error rate stayed below the threshold for thirty minutes.

If the signal changes, the judgment can change too. That is not inconsistency; it is a release decision tied to current evidence.

Resources

• [ARTICLE] Cambridge Dictionary: Too - Review too + adjective + to + verb and how the pattern connects a degree with an impossible or blocked action.
• [ARTICLE] Cambridge Dictionary: Enough - Check the position of enough after adjectives and before nouns, with to + verb examples.
• [ARTICLE] Microsoft Writing Style Guide - State release boundaries concretely, including scope and evidence, instead of hiding a decision behind vague confidence.

Key Takeaways

• Use too + adjective + to + verb when a condition blocks an action: The change is too risky to ship globally.
• Use adjective + enough + to + verb when a condition meets a threshold: The canary is stable enough to expand.
• Put enough before a noun: We have enough evidence to proceed.
• “Safe enough” is sufficient for a particular scope, not a guarantee of perfect safety.
• Always connect the judgment to an action, scope, and signal when the release decision matters.