Developers speak a dialect. It sounds like English. It uses English words. But anyone who has spent enough time in stand-ups and planning meetings knows that the meaning underneath is often something else entirely.

I say most of these myself, so consider this a confession as much as a dictionary.

The status update section

❌ "It should be a quick fix." → I have not opened the file yet.

❌ "It's mostly done." → The first 80% is done. The second 80% starts tomorrow.

❌ "I'm just finishing up a few things." → I found something terrifying and I'm hoping to fix it before anyone asks.

❌ "It's done, I just need to test it." → It is not done.

❌ "No blockers." → I'm blocked, but I haven't admitted it to myself yet.

The diplomacy section

❌ "Interesting approach." → I would like to formally object, but politely.

❌ "Let's take this offline." → This conversation is about to become an argument, or I need to look up what you just said.

❌ "That's a known issue." → We all agreed to stop looking at it.

❌ "It's by design." → It's a bug, but now it has documentation.

❌ "Good question." → I'm buying three seconds to think of an answer.

The estimation section

❌ "Two days, maybe three." → A week, if nothing surprising happens. Something surprising will happen.

❌ "It's just a small change." (said by someone else) → It touches the database, the API, both mobile apps and a report someone runs once a year.

❌ "We'll refactor it later." → This code will outlive all of us.

❌ "It works on my machine." → I've done my part. The universe has not.

The 2026 edition

❌ "I used AI to speed it up." → It was very fast. Then I spent the afternoon understanding what it wrote.

❌ "I reviewed the AI's changes." → I read the summary it wrote about its changes.

❌ "The agent is handling it." → The agent has been confidently editing the wrong file for twenty minutes.

And the classics

❌ "Can everyone see my screen?" → Nobody can see the screen. Everyone can see the notification preview from a group chat.

❌ "Any questions?" → Please, nobody have questions. It's 4:55.

❌ "I'll have a look." → This could mean anything from "fixing it now" to "you will never hear about this again".

Okay, the useful bit

The jokes land because every one of these phrases is vague. "Mostly done", "quick fix" and "I'll have a look" sound like information, but they don't tell anyone what to expect. That's how a manager hears "two days" and a developer means "two days if the stars align", and both leave the meeting feeling misled.

The fix isn't better excuses. It's a better shape for the update. When someone asks about status, try answering with three things:

• ✅ Where it is, with evidence: "The API endpoint and tests are merged. The mobile screen isn't started."
• ✅ What could change the plan: "The payment gateway sandbox is flaky, which might slow testing."
• ✅ When you'll know more: "I'll have a firm date by Thursday's stand-up."

Notice that none of this needs a confident estimate. It's honest about uncertainty, which is exactly what "should be a quick fix" tries to hide. And it saves you from the worst meeting phrase of all, the one said two weeks later: "So... what happened?"

Which phrase did I miss? I'm sure your team has a few of its own, and I'd love the translations.