No ETA
You were directed here because you probably don't understand that there is no ETA.
2024-09-02 14:23:15 you: When will this be ready?
2024-09-02 14:23:18 dev: There's no ETA.
2024-09-02 14:23:22 you: But approximately when?
2024-09-02 14:23:25 you: Like ballpark?
2024-09-02 14:23:28 you: Even just a rough estimate?
## DEV GETS INCREASINGLY FRUSTRATED
It's like asking "Are we there yet?" when the destination doesn't exist!
When we say "No ETA" we mean:
2024-09-02 14:23:15 you: When will this be ready?
2024-09-02 14:23:18 dev: There's no ETA.
2024-09-02 14:23:22 you: Understood, thanks!
Note how much simpler that was, and nobody got frustrated!
What "No ETA" Actually Means
No ETA means No Estimated Time of Arrival. It means:
- We don't know when it will be done
- We can't give you an estimate
- Not even a rough one
- Not even a ballpark figure
- There is no timeline
- It's done when it's done
Asking for "just a rough estimate" or "approximately when" defeats the entire purpose. If we had any kind of estimate, we would have given it to you.
Why There's No ETA
Projects often have no ETA because:
- The scope is undefined or constantly changing
- We're waiting on external dependencies
- Technical challenges are unpredictable
- It's research/experimental work
- Resource allocation is uncertain
- It's not the current priority
Pushing for an ETA when there isn't one typically results in:
❌ Made-up dates that will definitely be missed
❌ Frustrated developers
❌ Unrealistic expectations
❌ Wasted time explaining why there's no ETA
What You Should Do Instead
If you need to plan around something with no ETA:
✅ Plan assuming it won't be ready
✅ Ask for progress updates periodically
✅ Discuss alternatives or workarounds
✅ Accept that some things take an unknown amount of time
Remember: No ETA doesn't mean never. It means we honestly don't know when, and that's okay.