5 exercises on time and sequence adverbs that describe execution order, loading strategy, and temporal relationships in concurrent and asynchronous systems.
Key async/concurrent adverb collocations
concurrently execute — multiple tasks in progress at the same time
sequentially process — one at a time, in order; opposite of concurrently
lazily evaluate — compute only when result is needed
eagerly load — load upfront at init time; the lazy/eager pair is canonical
retroactively applied — effect applied to past data/events
0 / 5 completed
1 / 5
A concurrent system design document states:
"The API server handles up to 500 requests ___ — each request is processed in its own goroutine without blocking others."
Which time/manner adverb describes multiple operations happening at the same moment in parallel?
Concurrently execute is the canonical technical collocation. "Concurrently" is the standard adverb in computing for tasks that are in progress at the same time — whether truly parallel (on multiple cores) or interleaved (on a single core). It is the adjective/adverb form of "concurrency," one of the fundamental concepts in operating systems, Go, Erlang, and async frameworks.
Key distinctions in IT:
concurrently — multiple tasks in progress at the same time; standard term ✅
simultaneously — at exactly the same instant; often implies true parallelism; "simultaneously" is correct but "concurrently" is the technical term of art
parallelly — not a standard English adverb; the adjective is "parallel" / adverb form is "in parallel"; never used in professional writing
jointly — together, cooperatively; describes collaboration, not concurrency
Common collocations:
run concurrently
execute concurrently
concurrent requests
concurrency limit
2 / 5
A data pipeline specification reads:
"The ETL jobs must run ___ — job B cannot start until job A has completed and written its output to the staging table."
Which adverb describes tasks that must complete one after another, in a defined order?
Sequentially process is the canonical collocation. "Sequentially" means in a defined order, one after another, each step waiting for the previous one to complete. This is the opposite of concurrent/parallel processing and is the standard term in pipeline design, ETL, and algorithm analysis.
Key distinctions:
sequentially — in sequence, one at a time, in order ✅ — the standard technical term
linearly — in a straight line; in computing, "linear" usually describes time complexity O(n), not execution order
orderly — in an organised manner; too vague; describes manner, not sequential execution
serially — one at a time; technically accurate (serial vs parallel) but less common than "sequentially" for pipeline context
The fundamental pair:
sequentially — one at a time, in order
concurrently / in parallel — multiple at the same time
Common collocations:execute sequentially, process records sequentially, sequential consistency.
3 / 5
A Haskell/Scala developer explains a performance optimisation:
"We changed the data loading strategy to ___ evaluate — the collection is computed only when a value is actually needed, not when it is defined."
Which adverb describes a computation strategy that defers work until the result is actually required?
Lazily evaluate is the precise technical term. Lazy evaluation (also: lazy loading, deferred evaluation) means a computation is not performed until its result is actually needed. This is a fundamental functional programming concept (Haskell is lazy by default) and is used in many contexts: lazy sequences, lazy loading of images, lazy instantiation of singletons.
Why "lazily" is the fixed adverb:
lazily — the standard adverb form of "lazy evaluation" / "lazy loading" ✅
deferred — used as an adjective ("deferred execution") but "deferred evaluate" is not an idiomatic collocation
passively — implies no action; not a technical term for evaluation strategy
slowly — describes speed, not the deferral strategy
The canonical pair:
lazily evaluate / lazy evaluation — compute on demand
Common collocations:lazy loading, lazy initialisation, lazy sequence.
4 / 5
A frontend performance guide recommends:
"Avoid ___ loading all route components at startup. Use code splitting so each route's bundle is loaded only when the user navigates to it."
Which adverb describes loading resources immediately and proactively, before they are needed?
Eagerly load is the established technical term, forming the canonical opposite pair with lazily load. Eager loading means fetching or computing all resources upfront, at initialisation time, regardless of whether they will be needed immediately. This increases startup time but reduces later latency. The term is widely used in ORM contexts (eager vs lazy loading of database relations), frontend bundling, and dependency injection.
aggressively load — informal; occasionally used colloquially but not the standard term
greedily load — not a standard collocation; "greedy" is used in algorithm analysis (greedy algorithm), not loading strategy
proactively load — describes the intent, not the technical pattern name
Common collocations:eager loading in ActiveRecord / Hibernate, eager vs lazy fetching.
5 / 5
A database migration post-mortem reads:
"The foreign key constraint was ___ applied to existing rows after the migration — it was not part of the original schema and was added three days later."
Which adverb describes something applied after the fact, to data or events that already occurred?
Retroactively applied is the precise term. "Retroactively" means with effect from a time in the past — applied to things that already happened or existed. In database contexts, retroactively applying a constraint means enforcing it on pre-existing data. In law and policy, "retroactive" means changing the rules for things that already occurred. This is the technical and formal term.
Key distinctions:
retroactively — applied to past events/data; formal, precise ✅
subsequently — after something else happened; describes sequence, not backward application: "the constraint was subsequently added" means it came after, but doesn't imply effect on past data
belatedly — later than it should have been; informal; implies delay/failure
later — simple time reference; too informal for technical documentation