Too, Enough, So, and Such

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

• Use too, enough, so, and such to describe a technical limit, capacity, or consequence.

• Keep the difference between too large to..., large enough to..., so large that..., and such a large...that... visible.

• State what a system can or cannot do without turning one threshold into a universal judgment.

• Rewrite a vague performance note as a bounded recommendation with an explicit trade-off.

Idea in one sentence: These degree words connect a measured property to a practical consequence: a value can block an action, permit an action, or produce a result.

Core Insight

Consider a team moving 48 million rows into a new table. The migration tool can process 200,000 rows per batch, but the first draft tries to run the whole job at once:

The migration is too large to run in one batch.

Too large is not a decorative intensifier. It means the size crosses a practical limit for the action that follows. The limit might come from lock duration, memory, transaction logs, or the maintenance window. A useful next sentence makes the alternative visible:

The batches are small enough to complete within the maintenance window.

Now the writer describes both sides of the constraint: one unit cannot fit safely, while a smaller unit fits the available time. The choice still has a trade-off. Smaller batches reduce lock pressure but add coordination and checkpoint overhead.

From Equality to Degree and Consequence

Lesson 011 compared two options on one property:

The shared cache is as fast as the local cache on the median path.

This lesson adds a consequence to the property:

The migration is too large to run in one batch.
The batch is small enough to complete in ten minutes.
The table is so large that the job needs checkpoints.
It is such a large table that a single transaction would exceed the log budget.

The words answer slightly different questions:

The grammar gives the reader a relationship between a measurement and an action or result. The engineering work is choosing the right threshold and naming it when the reader needs to verify it.

The Small Situation: A Batch Migration

The team measures three possible batch sizes:

The status update should not only say that the first plan failed. It should show why and what the team changes:

The 2-million-row batch is too large to finish within the 10-minute window.
The 500,000-row batch is small enough to finish with a four-minute lock.
The table is so large that the migration needs checkpoints between batches.

The final sentence uses so...that to connect scale to a requirement. It does not claim that every large table needs the same checkpoint interval. The interval depends on the lock budget, log capacity, and recovery plan.

The Naive Idea: Degree Words Are Just “Very”

A literal translation can treat too as a stronger version of very:

The migration is very large to run in one batch.

That sentence is not natural for this meaning. Very large describes degree but does not say what the size prevents. Use too...to when the degree crosses a limit:

The migration is too large to run in one batch.

The opposite mistake is to use too for every difficult case:

The 500,000-row batch is too small to finish safely.

If it actually completes within the window, the writer may mean small enough:

The 500,000-row batch is small enough to finish safely within the window.

Too points to a blocked or undesirable consequence. Enough points to a threshold that has been met. Neither word chooses the engineering threshold for you.

The Form: Too and Enough

Place too before an adjective or adverb:

too large
too slow
too expensive to operate
too quickly to inspect

The common action pattern is:

subject + be + too + adjective + to + verb

Examples:

The payload is too large to fit in one message.
The query is too slow to run on every request.
The alert is too noisy to page the on-call engineer.

Place enough after an adjective or adverb:

large enough
fast enough
reliable enough
quickly enough

Use the same to + verb continuation:

The payload is small enough to fit in one message.
The query is fast enough to run on the read path.
The signal is reliable enough to trigger an automated rollback.

With a noun, enough comes before the noun:

We have enough memory to run the index build.
The worker has enough capacity to drain the queue before midnight.

Avoid memory enough or capacity enough in these sentences. The placement changes with the word being modified.

The Form: So and Such

Use so before an adjective or adverb, often followed by that and a result:

The queue is so deep that the autoscaler added four workers.
The query is running so slowly that the request times out.
The signal changed so quickly that the dashboard missed the first spike.

Use such before a noun phrase, also often followed by that:

It is such a deep queue that the autoscaler added four workers.
It was such an expensive query that the team moved it to a batch job.
They caused such large log files that retention had to change.

The article matters with a singular countable noun:

such a large table
such an expensive query

With plural or uncountable nouns, do not add a:

such large tables
such expensive queries
such high latency

So large and such a large table describe the same general degree from different grammatical angles. Choose so when the adjective is the focus; choose such when the noun phrase is the focus.

Name the Threshold, Not Just the Feeling

A sentence with too or enough is strongest when the reader can find the threshold behind it. Compare:

The query is too slow.
The query is too slow for the 200 ms API budget.

The second sentence tells the reader what “too” means. It also leaves room for another context where the same query might be acceptable, such as an overnight report.

The same principle applies to enough:

The worker has enough capacity.
The worker has enough capacity to drain the queue before the maintenance window ends.

The consequence supplies the requirement. If the requirement changes from a maintenance window to a user-facing latency target, the sentence needs a different boundary.

Use so...that when the consequence is already observed:

The queue was so deep that the service delayed notifications for six minutes.

Use too...to when the consequence is a blocked or rejected action:

The queue is too deep to drain before the window closes.

These sentences can describe the same system at different moments: one reports what happened, and the other states what the current limit prevents.

A Worked Performance Note

An API gateway accepts file uploads. The current limit is 10 MB per synchronous request. A client team proposes a 40 MB JSON payload. The first note is vague:

The payload is very big and the endpoint is not good for it.

Repair it in passes.

Pass 1: State the blocking relation

The payload is too large to send through the synchronous endpoint.

Pass 2: Name the boundary

The 40 MB payload is too large for the gateway's 10 MB synchronous limit.

Pass 3: Offer a feasible alternative

The upload is small enough to send through object storage in chunks.

Pass 4: State the observed consequence and trade-off

The payload is so large that the client needs resumable uploads. This adds client-side state, but it avoids holding a long synchronous request open.

The final note does more than select a grammar pattern. It explains a system boundary, a new action, an observed consequence, and the cost of the workaround.

The same review habit works for capacity claims. Ask what resource is being measured, what event consumes it, and which deadline or safety budget sets the limit. A sentence such as The worker has enough capacity is unfinished until the reader knows enough for what: draining a queue, serving a peak, or recovering after a failure.

Common Confusions

Confusion: too means “very”

Why it is tempting: both words increase degree.

Better model: too normally connects degree to an unwanted limit or blocked action. Use very when you only want to describe intensity.

Confusion: enough goes before the adjective

Why it is tempting: Spanish often places the equivalent of “enough” before the property.

Better model: say fast enough, reliable enough, and large enough; put it before a noun in enough memory or enough capacity.

Confusion: so and such are interchangeable everywhere

Why it is tempting: both can introduce a consequence with that.

Better model: use so + adjective/adverb (so slow) and such + noun phrase (such a slow query).

Confusion: the threshold is obvious to everyone

Why it is tempting: the team may have discussed the budget in a meeting.

Better model: include the limit when the sentence enters a ticket, design note, or incident record. A future reader should not have to guess what too slow means.

Confusion: too automatically means “do not do it”

Why it is tempting: the pattern often describes a blocked action.

Better model: state the action and the alternative. Too large to send synchronously can lead to a chunked upload; the modifier identifies the constraint, not the final product decision.

Check Your Understanding

Check: Which sentence expresses a blocked action with too?

A. The payload is too large to fit in one message.

B. The payload is large enough to fit in one message.

C. The payload is so a large that it fits in one message.

Think first, then reveal.

Answer: A. Too + adjective + to links an excessive degree to an action that cannot safely happen.

Check: Which sentence uses enough correctly?

A. The worker has capacity enough to drain the queue.

B. The worker has enough capacity to drain the queue before midnight.

C. The worker has enough to capacity drain the queue.

Think first, then reveal.

Answer: B. Enough comes before the noun and the to clause states the requirement.

Check: Which pair uses so and such correctly?

A. The queue is so deep that workers are scaling out. It is such a deep queue that workers are scaling out.

B. The queue is such deep that workers are scaling out. It is so a deep queue that workers are scaling out.

Think first, then reveal.

Answer: A. So modifies the adjective; such introduces the noun phrase such a deep queue.

Practice: Rewrite a Deployment Note

A deployment note contains four vague lines:

The database is very busy. The batch is big. We have lots of workers. The queue has a lot of messages.

The evidence is more specific:

• the database has a 70% CPU budget for the migration;
• the proposed batch takes 12 minutes, but the lock budget is 5 minutes;
• six workers can drain the queue before the maintenance window;
• the queue is deep enough to trigger autoscaling.

Rewrite the note in four sentences:

1. use too...to for the batch limit;
2. use enough + noun for worker capacity;
3. use so...that or such...that for the queue consequence;
4. include a recommendation and its trade-off.

One possible answer is:

The proposed batch is too large to finish within the five-minute lock budget. Six workers provide enough capacity to drain the queue before the maintenance window ends. The queue is so deep that autoscaling has started. Use smaller batches to protect the lock budget, although they require more checkpoints and coordination.

A good revision ties every degree word to a consequence or threshold. It does not use too as a synonym for “large,” and it does not hide the cost of the safer plan.

Daily Practice Lines

• The migration is too large to run in one batch.
• The worker has enough capacity to drain the queue before midnight.
• The shared cache is as fast as the local cache on the median read path.

The first line is the anchor for this lesson. The second varies the direction from a blocked action to a met requirement. The third retrieves the equality pattern from lesson 011 so that degree and comparison remain connected but distinct.

Resources

• [ARTICLE] Cambridge Dictionary Grammar: Too, enough, so, and such - Focus: place degree words with adjectives, nouns, and consequence clauses.
• [ARTICLE] Microsoft Writing Style Guide: Grammar - Focus: state limits, requirements, and operational consequences directly.

Key Takeaways

• Use too + adjective + to when a degree crosses a limit for an action.
• Use adjective + enough + to or enough + noun + to when a requirement is met.
• Use so + adjective/adverb + that and such + noun phrase + that to connect degree with an observed result.
• Name the threshold, workload, or time window behind too and enough whenever the reader needs to verify it.
• A degree word identifies a constraint; a good technical note also states the workaround and its trade-off.