Review: Modifiers in Design Notes

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

• Place focus modifiers such as only, still, already, and just so the reader knows what they limit.

• Combine frequency, degree, and comparison modifiers without accidentally changing the technical claim.

• Detect a scope ambiguity in a short design note and rewrite it with the intended meaning.

• Keep a modifier close to the verb, noun, or property it actually describes.

Idea in one sentence: A small modifier can change which part of a design note is true, so its position is part of the technical meaning.

Core Insight

Consider an admin endpoint that is rarely used but still needs authentication. The team has just finished a migration, and the endpoint already accepts the new token format. A draft note says:

The rarely used admin endpoint still needs authentication.

This sentence is clear because each modifier has a visible job. Rarely used describes frequency. Still says that authentication remains necessary even though the endpoint is uncommon. Move still, and the claim changes:

Still, the rarely used admin endpoint needs authentication.

This version makes still a transition from a previous point, not a modifier of the endpoint's current state. Both versions can be correct, but they organize the reader's attention differently.

Design notes often fail when the modifier is treated as a loose decoration. Compare:

Only the worker retries the notification.
The worker only retries the notification.
The worker retries only the notification.

The first limits the subject: no other component retries. The second can limit the action: the worker does not do more than retry. The third limits the object: it retries notifications, not payments or other messages. The word is small; the architecture claim is not.

The Modifier Toolkit

Use the earlier lessons as a set of review questions.

Frequency: how often?

Frequency adverbs usually sit before the main verb and after be:

The service rarely retries a completed payment.
The endpoint is rarely used.
The worker usually waits for an acknowledgement.

The frequency claim needs a time window when the note depends on evidence:

The endpoint was rarely used during the last 30 days.

Rarely is not the same as never. Do not turn a low count into an absolute guarantee.

Degree: how much?

Degree modifiers calibrate a property:

The indexed query is slightly faster on median latency.
The queue worker is much more resilient during retries.
The payload is too large for the synchronous endpoint.
The worker has enough capacity to drain the queue.

The modifier should match the evidence. If the measured difference is 3 ms, slightly faster may be reasonable; dramatically faster needs a stronger boundary.

Focus: what exactly is limited?

Only, still, already, and just change focus or time:

Only the API adapter changes the client.
The API adapter only changes the client configuration.
The migration still needs a checkpoint.
The migration already has a checkpoint.
The worker has just started draining the queue.

The safest placement is close to the thing being limited. If the placement is not enough, rewrite the sentence and name the noun again.

Comparison: how does one option relate to another?

Comparatives and superlatives also act as modifiers:

The indexed query is faster than the full scan on median latency.
The queue-worker rollback is the safest of the three under retry bursts.
The shared cache is as fast as the local cache in the canary.

Keep the property and comparison boundary visible. A modifier cannot repair a missing metric or an unknown candidate set.

A Scope Review in Four Passes

Use this process before approving a design note.

Pass 1: Circle the modifier

Find words such as only, still, already, just, usually, slightly, too, or enough. Ask what noun, verb, property, or time relation the writer intends to modify.

The worker only retries the notification.

Does only limit the action, the object, or the worker's role? If a reviewer could answer in two ways, the sentence needs repair.

Pass 2: Move the modifier to test the meaning

Try two placements and describe the difference:

Only the worker retries the notification.
The worker retries only the notification.

The first says that the worker is the sole retrying component. The second says that the notification is the sole object being retried. This move is a quick diagnostic: if the meaning changes, position matters.

Pass 3: Check the evidence boundary

Frequency and degree words need a context:

The service usually recovers quickly.

Usually when? During normal deploys, after database failover, or in the last seven incidents? Add the boundary when it changes the decision:

The service usually recovers within two minutes after a routine deploy, but failover recovery is slower.

The modifier is now calibrated instead of sounding like an unsupported promise.

Pass 4: Check the trade-off and next action

A precise modifier often reveals a design choice:

The endpoint is rarely used, but it still needs authentication because it can change production data.

The low frequency does not remove the security requirement. The trade-off is a small maintenance cost for protection against a high-impact action.

Work Through a Design Note

Draft:

Only the worker usually retries the payment notification and it still sometimes fails.

This sentence contains two scope problems. Does only limit the worker, the action, or the payment notification? What does usually modify? What is the time window for sometimes?

The incident facts are:

• the worker is the only component allowed to retry notification delivery;
• it retries most transient API failures;
• it never retries a confirmed payment charge;
• five of the last 200 notifications failed after the retry limit.

Rewrite the note in three steps.

Step 1: State ownership of the action

Only the worker retries notification delivery.

Now only clearly limits the subject.

Step 2: State frequency with a boundary

The worker usually retries transient API failures during delivery.

Usually modifies the retry behavior, and during delivery keeps the event context visible.

Step 3: State the exception and the evidence

It never retries a confirmed payment charge. Five of the last 200 notifications still failed after the retry limit.

The final note distinguishes an absolute safety rule (never retries a confirmed charge) from a measured residual failure (five of 200). It does not hide the trade-off: retries improve delivery success for transient failures but cannot guarantee delivery after every limit is exhausted.

Position and Tone in Design Notes

Modifiers also control how confident or urgent a sentence sounds. Compare:

The migration has already passed the dry run.
The migration just passed the dry run.

Already emphasizes that the event happened earlier than expected or before the current step. Just emphasizes recency. Neither one proves that the migration is ready for production. Add the next check:

The migration has already passed the dry run, but the team still needs a rollback test.

The word still keeps an outstanding requirement visible. This is useful in design reviews because a completed milestone can otherwise sound like a complete approval.

Use degree modifiers with the same care:

The new parser is slightly more accurate on the validation set.

The sentence is narrower than:

The new parser is much better.

The first identifies a metric and dataset. The second invites an argument about an undefined property.

Common Confusions

Confusion: only has one fixed meaning

Better model: only limits the nearest intended element, but English placement can leave scope ambiguous. Move it or rewrite the sentence when the architecture claim matters.

Confusion: still always means “continue” in the same place

Better model: still can modify a continuing state (still needs auth) or act as a discourse transition (Still, the endpoint needs auth). Use context and position to show which job it performs.

Confusion: already means “approved”

Better model: already marks an earlier completed event. The migration already passed the dry run does not mean that it passed the rollback test.

Confusion: frequency words are facts without a denominator

Better model: usually, rarely, and sometimes become useful when the time window or count is available. Five of the last 200 is often clearer than sometimes.

Confusion: more modifiers make a sentence more precise

Better model: each modifier should have one visible job. Remove words that do not change the decision or replace them with a metric, condition, or noun.

Check Your Understanding

Check: What does this sentence most directly say?

Only the worker retries the notification.

A. The worker is the only component that retries it.

B. The worker retries only one notification and no other object.

Think first, then reveal.

Answer: A. Only is placed before the subject, so it limits which component performs the action.

Check: Which sentence keeps the frequency boundary visible?

A. The service usually recovers quickly.

B. The service usually recovers within two minutes after a routine deploy.

C. The service always recovers.

Think first, then reveal.

Answer: B. It says what usually means and under which event it was measured.

Check: Which note preserves completed work and remaining work?

A. The migration already passed the dry run, so it is approved.

B. The migration has already passed the dry run, but the team still needs a rollback test.

Think first, then reveal.

Answer: B. Already marks a completed step; still keeps the outstanding requirement visible.

Practice: Repair a Modifier-Heavy Note

Repair this note using at least four modifiers precisely:

The new endpoint only usually works and still just has a much better cache.

Facts:

• only the gateway calls the endpoint;
• it succeeds in 98 of the last 100 canary requests;
• the cache is 20 ms faster on median reads;
• the cache has already been tested, but invalidation during failover is still open.

One possible answer is:

Only the gateway calls the new endpoint. It succeeded in 98 of the last 100 canary requests, so it usually works under that workload. The new cache is 20 ms faster on median reads, but invalidation during failover is still untested. The cache has already passed the basic test; the team still needs the failover test.

This revision removes just and much better because the numbers carry their meaning more clearly. It places only, usually, already, and still next to the facts they modify.

Daily Practice Lines

• Only the worker retries notification delivery.
• The migration has already passed the dry run, but it still needs a rollback test.
• The indexed query is slightly faster on median latency for the customer workload.

Read each line once with the modifier removed, then restore it. Notice which part of the claim becomes weaker, narrower, or ambiguous without the modifier.

Resources

• [ARTICLE] Cambridge Dictionary Grammar: Adverbs and adverb position - Focus: place frequency, degree, and focus adverbs near the words they modify.
• [ARTICLE] Microsoft Writing Style Guide: Grammar - Focus: make scope, emphasis, and technical conditions explicit.

Key Takeaways

• Modifier position can change the subject, action, object, or time relation in a design note.
• Place only, still, already, and just near their intended target; rewrite when placement remains ambiguous.
• Calibrate usually, rarely, slightly, and much with a workload, count, metric, or time window.
• A completed step (already) does not erase an outstanding requirement (still).
• Review modifiers as technical evidence: each one should narrow, qualify, or connect a claim that matters to the decision.