“So… how long will this take?”

Every developer knows this question. And every honest answer starts with: “It depends.”

Not because we don’t understand the work, but because we understand the risk.

Software estimation isn’t math. It’s educated guessing with a confidence score. Remember that!

Yet, we keep making the same mistake: giving a single number.

“It will take three days.”

The moment you say that, you turn a guess into a deadline. You set yourself up to fail because you didn’t account for the unknown. That’s when reality hits: Legacy code, weird bugs, broken APIs.

And suddenly, that “3 days” evaporates. And so does trust.

What clicked for me was to stop giving single numbers and start giving a range, attaching the “why.”

Instead of: “I’ll have this done by Friday.”

Try this: “Best case, this is done by Friday. But if the payment gateway integration is messy, it pushes to Tuesday. I’ll know more once I make a spike.”

This approach changes the dynamic:

• It treats estimation as a probability, not a promise.
• It shows you understand the system’s complexity.
• It protects your credibility when things inevitably go wrong.

A senior+ engineer isn’t someone who codes faster. It’s someone who knows that “just a quick change” rarely stays quick.

Protect your credibility.