When you write code reviews, issue reports, or team messages, choosing between worry and be worried depends on what you want to say. You might describe an ongoing habit, an emotional state at this moment, or an event that causes concern. Picking the right form helps your teammates understand whether an issue is a routine concern or an urgent reaction to a specific change.
Describe an ongoing habit with worry
Use the simple verb worry when you describe a regular habit, a general tendency, or repeated behavior over time. An everyday English sentence illustrates this pattern: Marcus worries about parking whenever he drives into the city center. In software teams, use this same form to describe how developers regularly react to recurring situations, such as running migrations, deploying releases, or reviewing large changes.
Our backend team worries about connection pool limits whenever we run batch migrations.
This sentence describes an ongoing habit and a recurring reaction during batch jobs, so it uses the simple verb worry.
Describe a current emotional state with be worried
Use be worried when you describe a personal emotional state at a particular moment. The statement Sandra is worried describes how Sandra feels at this exact moment about a specific problem. In pull requests and incident channels, use this adjective pattern with the verb be to state your present feeling about a failing test, a security alert, or an active service regression.
I am worried about this unhandled null pointer exception in the checkout service.
This sentence describes the author's current emotional state right now about one specific bug, so it uses be worried.
Describe an event that causes concern with worry
Use worry as a transitive verb when an event, change, or technical finding causes concern to someone. In this pattern, the event itself is the subject that creates concern for the team. In engineering discussions, a dropped connection, a memory leak, or a broken build can worry an engineer who is investigating a problem or reviewing code.
The sudden latency spike in the authentication service worries our on-call engineers.
This sentence describes an event that causes concern, where the latency spike directly causes concern to the engineers, so it uses worry with an object.
Before you send a code review comment or incident update, check what you want to emphasize. If you describe a repeated habit across sprints, use the verb worry. If you describe an emotional state right now about a specific bug, use be worried. If a system event or alert causes concern, use worry with that event as the subject.
Practice: Worry or be worried: which one fits?.
Top comments (0)