... and assuming that the listener is able to parse and then object to phrasing on the fly. Phrasing can matter, but fine-grained hypercriticism is mostly a useless exercise.
I think it's partially the tone of blame towards the use of "just". While I am interested in micro-optimizations, especially in how I communicate, I suspect most people don't. I don't begrudge anyone who uses "just" in speech though.
Another article / perspective on this would be written to help others understand why they or others use "just" in speech. This would help people interested in optimizing communication see the flaws in the use of the word, while aiding in understanding/empathy for this who are on the receiving end.
"Could you just cache the hot partition keys?" probably doesn't carry any negative baggage when it's said by someone you trust to be empathetic to your situation. i.e. You know they aren't underestimating your abilities, you trust they earnestly want to help, and you know you can ask them for help without being judged.
The "Stuck" example is different. The "just" underestimates the difficulty for the listener. So the speaker may respect their abilities and earnestly want to help, but they've underestimated the challenges of their disability -- and overcoming the challenge is not as simple as asking for help.
However, in both cases, the statements work the same without the word "just". Given how little information it adds and the risk of getting it wrong, I think I'll try to use "just" a little less.
"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.
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.
It means don't sit there thinking about how I said "just". Or how it means I think you're dumb. It means just fucking do it. Just do it. Do it.
The people I've enjoyed working the most have just sat down and done it. Difficult things too. Things that took time. They just did the work. So stop thinking about the shenanigans and just do it.
It's sad and funny how much people will fight the words and spend time arguing this is too crass or not kind instead of just doing it.
This is my hill I guess.
It is, however, rare that telling someone else "just do it" gives them that attitude. I have never seen it happen. I have said "just..." and seen the effect described in the article.
Asking questions, developing an understanding of what may be holding someone else back from "just doing it", then offering them any help you can provide them is much more likely to help them develop the attitude, in my experience.
- I don't yet understand why steps x, y, z are necessary. To me it would seem simply/naively doing ... might work but I'm probably missing something.
- Would a simpler (though possibly not perfect) solution suffice here.
- I think we can do ... here and it'll be fine. Should we / let's see if that works, and revisit ? / .
Sure, "just do it" would often be bad, indicating a variety of things like "stop dwelling on this or arguing, do what I say". Or "can you just quickly do this (thing I find trivial but don't understand at all) for me", but in the end it's the context that matters.
Like, I can turn this around as well. The word "don't" is negative and should be avoided at all cost. Better: "could we try ... instead of ..." (see submission title).
Then conclude "don't worry about it" should not be said. Which to be fair is also true in some contexts but again, context!
EDIT: To be clear it is valuable for me to learn that usage of "just" could be problematic. That's important when not knowing the other party but among coworkers I also happen to have more of a relationship with than just one-off comments, these kind of word choices are not what make or break things. Especially in a diverse environment I assume everyone is acting in good faith and I would only let word choices affect me if the sum of my interactions with a coworker has been negative already and I "know" they are trying to incite an argument.