DEV Community: MicroEnglish

Main, helping, or linking verb: what does each do in a developer message?

MicroEnglish — Thu, 08 Oct 2026 10:41:49 +0000

When you write a code review or report a bug, check what the verb tells your reader. Does it name an action, help another verb, or connect the subject to a description? Look at the verb in the whole sentence: the same word can have different roles.

Find the main verb that names the action

Start by asking what happened or what someone did. In the supplied lesson sentence, reviewed names the action completed by the operations director. A main verb carries the central meaning of the verb phrase. For an action in a code review, identify both the person or thing doing it and the verb that names it.

The reviewer checked the error message before approving the change.

Checked is the main verb in the main clause: it tells us what the reviewer did. Its past form places that action in the past. The phrase beginning with before adds information about the sequence. When checking a longer review comment, find the central action first, then read the details around it.

Keep helping verbs with the verbs they support

A helping verb works with a main verb. Read the words together to understand the action and its timing. Looking only for a word with an action meaning can make you miss part of the message. In an issue update, that missing part may distinguish work happening now from a completed action.

The developer is checking the failing test.

Checking names the action, and is helps form the present continuous. Together, is checking describes an action in progress. Is does not connect the developer to a description here; it supports checking. If you identify the verb phrase in this update, include both words.

Recognize linking verbs that introduce a description

A linking verb connects the subject to information about that subject. It can be the sentence's main verb, so main and linking are not always separate categories. To distinguish a linking use of is from a helping use, check what follows: does it describe the subject, or form an action with another verb?

The error message is unclear.

Unclear describes the error message. Is links that subject to its description and is the main verb here. This review comment describes a condition; it does not say that someone is performing an action. Compare its structure with the previous example, where is supports checking.

Before sending a developer message, underline the whole verb phrase. Check whether it names an action, includes a helping verb, or links the subject to a description.

Practice: Types of Verbs: Main Helping Linking.

Into, through, or toward: how should you describe movement in a bug report?

MicroEnglish — Tue, 06 Oct 2026 10:41:34 +0000

Choose the preposition that tells your teammate what the moving object actually does. In a bug report about a game character or a code review for a delivery simulation, entering a room, passing through a gate, and heading in a direction describe different behavior. Name the movement precisely so the reader can identify what to check.

Use into for crossing a boundary to the inside

Use into when something moves from outside a place to inside it. The boundary can be a doorway: stepped into describes crossing that boundary into the room. In an issue report, this distinction helps you say whether a character entered a restricted area or only approached it. Name the place after into so the reader knows which boundary matters.

The player character stepped into the locked room before the door opened.

This fictional bug report describes the character crossing into the room. The reported problem is entry before the door opens. Replacing into with toward would change the report: movement in the room's direction would not establish that the character crossed the doorway.

Use through for movement through a passage

Use through when the route passes through an opening or passage, such as a security gate. In developer communication, identify the passage when its role in the route matters. A report that only names the destination may leave out the point where the behavior went wrong.

In the delivery simulation, the van drove through the security gate while the barrier was down.

This fictional issue identifies the gate as the passage the van used. Through makes the crossing part of the reported behavior. The barrier's position explains why that crossing needs investigation; merely heading toward the gate would describe a different event.

Use toward when direction is the point

Use toward to describe movement in the direction of a place. Toward does not by itself say that the moving object arrives there or enters it. In a review comment, keep a direction check separate from an arrival or entry check. Otherwise, the wording can suggest that the test establishes more than it does.

Please check that the robot moves toward the charging room when this function runs.

This fictional review comment asks about the robot's direction. It does not ask whether the robot crosses the doorway. If entry is the behavior you need to check, into would express that additional movement across the boundary.

Before sending the message, check what the observed movement establishes: entry into a place, passage through an opening, or direction toward a place. Choose the preposition that matches that evidence.

Practice: Prepositions of Movement: Choose the Route.

How do you use above board in developer messages?

MicroEnglish — Thu, 01 Oct 2026 17:46:31 +0000

Use above board when you mean that a process or action is open, honest, and free from deception. In a code review, issue report, or team message, make clear which decision or process you mean. Keep the expression together, and don't add the before board.

Describe an honest, open process

Above board describes how people handle something. Use it when the point is openness and honesty, such as explaining how a team chose a contractor or approved a purchase. Give the reader a concrete reason for the description. A statement about what people disclosed is more useful than an unexplained claim that everything was above board.

The contractor selection was above board: we shared the evaluation criteria and disclosed each reviewer's connection to the candidates.

This fictional team message describes an open selection process. Sharing the criteria and disclosing connections explain why the writer calls it above board. The expression concerns honesty in the decision, not whether the selected contractor will deliver good code.

Keep the out of the expression

Write above board as two words, without the between them. When describing a process, you can place the expression after was or is. If you're drafting a comment about an approval, name the approval first so the reader knows what you're describing. Adding the changes the wording and loses the intended idiom.

The payment approval was above board: the team recorded the amount, the reason for the payment, and who approved it.

This fictional issue comment uses above board directly after was. The details explain the openness of the approval. Board is part of the fixed expression here; it does not name a physical board that needs the.

Separate honesty from technical results

Use above board to discuss openness and freedom from deception, not physical position or financial success. In developer communication, also keep that meaning separate from a technical result. Passing tests and describing an honest review process are different claims. State the process you mean and give its relevant details.

The release review was above board: the team shared the failing test results before asking for approval.

This fictional team message describes honest disclosure during a release review. It does not say that the tests passed or that the release made money. Sharing the failures supports the intended meaning even though the technical problems remain.

Before sending, check that above board means open and honest in your sentence, that the process is clear, and that you haven't inserted the before board.

Practice: Above board.

How to Use 'Go Hand in Hand' in Code Reviews

MicroEnglish — Mon, 21 Sep 2026 03:01:38 +0000

In a code review or pull request, you might read: "Testing and refactoring go hand in hand."

This idiom means two practices are closely connected and often happen together. However, it does not mean they always happen together, and it does not prove that one causes the other. They are connected activities.

Grammar: "Go" vs. "Goes With"

Pay attention to your subject when using this phrase in team discussions:

Two concepts use go: "Testing and refactoring go hand in hand." Because the subject is plural (two actions), use go.
One singular concept uses goes + with: "Testing goes hand in hand with refactoring." Because the subject is singular ("Testing"), use the singular verb goes followed by the preposition with.

Plainer Alternatives for Clearer Communication

Idioms can sometimes create confusion on international teams. If you want direct, plain workplace English for your pull request comments, use these alternatives:

"Testing and refactoring work well together."
"Testing and refactoring are often done together."
"These two practices are closely linked."

Quick Check

Which sentence is grammatically correct?

Continuous delivery go hand in hand with reliable test suites.
Continuous delivery goes hand in hand with reliable test suites.

Answer: Sentence 2 is correct.
Reason: "Continuous delivery" is a singular noun phrase. It requires the singular verb goes and the preposition with before the second concept.

Author: MicroEnglish

If you want more practice with this expression:

Watch the full 8-minute video lesson, featuring four British and American listening conversations, replays, pause time to answer, pronunciation guidance, and six practical FAQs.
Try the interactive lesson at MicroEnglish. The first dictation exercise is free; further practice and AI tutor features depend on membership and available credits.