Blog · Jargon explained

15 developer phrases every project manager should understand


Software teams have their own language. Most of it is harmless shorthand, but some phrases carry real information about risk and timing. Here are fifteen you will hear often, what they mean, and what they mean for you.

1. "It works on my machine"

Meaning: The code runs on the developer's computer but fails somewhere else, such as the test or live environment. For you: A short investigation is needed. Usually hours, occasionally longer.

2. "It's in review"

Meaning: The work is written and waiting for another developer to check it in a pull request. For you: Not done yet. Reviews can sit for days if nobody is assigned.

3. "It's on staging"

Meaning: The change is on the test copy of the product. For you: Ready for checking. A good moment to look at it yourself before it goes live.

4. "We need a spike"

Meaning: A short, time-boxed research task to answer a technical question before choosing an approach. For you: A healthy sign. It reduces surprises. Ask how long the spike is boxed for.

5. "That's an edge case"

Meaning: An unusual situation that only happens sometimes. For you: Ask how often it would affect real users, then decide together whether to handle it now or later.

6. "We'll put it behind a feature flag"

Meaning: The code goes live but stays switched off until someone turns it on. For you: Good news. You control the timing of the launch separately from the release.

7. "We need to refactor first"

Meaning: Existing code needs to be cleaned up before new work can be added safely. For you: Extra time before the visible feature. Ask how much. See our guide to technical debt.

8. "It's a hotfix"

Meaning: An urgent fix to a live problem, released outside the normal schedule. For you: Something broke for users. Ask what happened and whether anyone needs to be told.

9. "We rolled back"

Meaning: A release was undone and the previous version restored. For you: The product is working again, but the new release is on hold.

10. "There's a regression"

Meaning: Something that used to work broke after a recent change. For you: Usually quick to fix once found, but a sign that testing missed something.

11. "The tests are flaky"

Meaning: Automatic checks sometimes pass and sometimes fail with no code change. For you: A hidden drag on speed. Worth supporting time to fix.

12. "We're hitting a rate limit"

Meaning: An outside service only accepts a certain number of requests, and the product is going over. For you: Can cause errors for users at busy times. Ask whether it needs a fix or a higher plan with the provider.

13. "That's scope creep"

Meaning: The work has grown beyond what was agreed. For you: This one is yours. Decide what to cut or move the date.

14. "It's a dependency"

Meaning: The work relies on something else: another team, a tool, a client or a third party. For you: A risk you may not control. Track it and follow up early.

15. "Story points"

Meaning: A rough measure of effort, compared with other work. Not hours. For you: Useful for comparing tasks and planning sprints, not for promising dates by themselves.

When the phrase isn't on this list

Developers combine these into long sentences, and that is where meaning gets lost. Paste the whole message into Plainlee and get it back in plain English, with the impact on your plan and the next question to ask. For single words, our tech glossary covers more than 40 common terms.