Fundamentals 7 min read

Why Does “Highly” Come Before “Likely”? The Grammar Logic Behind Adverb‑Adjective Order

The article explains why the adverb “highly” must precede the adjective “likely” by comparing word classes to programming parameters, detailing part‑of‑speech roles, the pre‑modification rule for adverbs, and the concept of collocations as language conventions.

Ops Development & AI Practice
Ops Development & AI Practice
Ops Development & AI Practice
Why Does “Highly” Come Before “Likely”? The Grammar Logic Behind Adverb‑Adjective Order

Introduction: Language as an API

Hello everyone, today we explore a seemingly simple yet logically deep question: in the sentence “It's highly likely that we'll need extra rehearsals,” why must the word highly appear before likely?

Think of language as an operating system with low‑level rules. For developers who work with code daily, understanding language structure is as interesting as understanding a framework’s API design.

Analogy: Function Parameters and Word Classes

In programming, the order of arguments matters. For example: calculate(base_value, multiplier) versus calculate(multiplier, base_value) Swapping the order can produce completely different results or errors. Language works similarly: each word has a part of speech, akin to a type or interface in a system.

Part‑of‑Speech “API”: Adverb vs. Adjective

Likely is an adjective . It describes the state of the subject “It,” indicating that the event is “possible.”

Highly is an adverb of degree . Its sole purpose is to modify the intensity of another word—here, the adjective likely .

Combined, highly tells us how strong the likelihood is.

Configuration‑File Analogy

event_probability:
  level: high   # role of "highly"
  base: likely   # the adjective itself

This mirrors the rule that an adverb that modifies an adjective is placed before that adjective, ensuring clear and unambiguous information flow.

Grammar Rule: Pre‑Modification by Adverbs

Adverbs that modify adjectives normally precede the adjective. This is a “pre‑modification” convention that keeps communication clear.

Examples: very fast (not fast very) incredibly simple (not simple incredibly) extremely efficient (not efficient extremely)

Thus highly likely follows this core grammatical protocol.

Collocations: “Convention Over Configuration” in Language

Software development often follows the principle “Convention over Configuration.” Language has its own conventions, called collocations , which are word combinations that feel naturally correct because they are widely used. highly likely is a strong, common collocation, just as we say “strong coffee” instead of “powerful coffee,” or “heavy traffic” instead of “dense traffic.”

Deeply concerned (深感担忧)

Fully aware (完全意识到)

Painfully slow (慢得令人痛苦)

Ridiculously cheap (便宜得离谱)

Learning these conventions makes our expression more native and efficient, just like using a mature framework speeds up development.

Conclusion: From Code Logic to Language Intuition

Returning to the original question, highly precedes likely for three reasons:

Role definition: highly is an adverb that modifies the adjective likely.

Grammar protocol: English syntax requires adverbs that modify adjectives to appear before them.

Language convention: highly likely is a widely accepted collocation, embodying the “convention over configuration” principle.

Next time you read technical documentation or write an email, notice these tiny language structures. Whether building complex software systems or crafting a simple sentence, clear logic, explicit rules, and efficient conventions are at work.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

grammarlanguage fundamentalsadjectiveadverbcollocationenglish usage
Ops Development & AI Practice
Written by

Ops Development & AI Practice

DevSecOps engineer sharing experiences and insights on AI, Web3, and Claude code development. Aims to help solve technical challenges, improve development efficiency, and grow through community interaction. Feel free to comment and discuss.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.