The job of the PM often demands creating project schedules, delegating assignments, spurring their team to deliver assigned tasks on time, and managing the team. It very much is their business to have some sense of how long things take, why they take so long, and get a sense whether the bottleneck is a personnel skill or motivation issue or the technical nature of the problem space.
A good faith answer would likely include an explanation why shipping a button took 3 weeks, would likely explain the relevance of those HTTP calls in your use case, and would help to give them a better sense of the work involved so they can better mentally cost out new interface items without creating expectations you’d be unlikely to meet.
No, but what I'm saying was that usage of "just" is not the issue, a shitty environment is. If your boss / coworker / PM doesn't use "just" but still makes it seem like a task should be easy to do in other ways (e.g. telling you your estimate is way too high for a task), does it really matter that much?
> "Why so long? It's just a button that does stuff. Can't you just..."
a) The problem is not the word "just", but that the person asks you something they consider simple. Changing the wording (removing "just") doesn't change the negative sentiment.
b) The "just" in the example does emphasize to the listener further that the speaker is underestimating the task at hand or doesn't yet grasp the full context. It can help the listener in identifying that they might have to spend some time to address that misconception in their follow-up reply.
"This feature will take about 3 weeks to ship."
"Why so long? It's just a button that does stuff. Can't you just..."
When the other side of the argument is a PM who can't describe what an HTTP call is, it's hard to look at it as a good faith discussion.