Hacker News new | ask | show | jobs
by m000z0rz 1321 days ago
> Communication is about being understood, not being fair.

This is why in some cases it's better to say "Just" instead of trying to hide what you're trying to say in order to maybe be more sensitive without even knowing if that's necessary.

For this situation, I tend to phrase it as "Can we just <x>"? which might be received better than "Just <x>", but "just" is an important word here - I want the other person to understand that I think this ought to be easy. If it's not, I probably want to know why, because that will give me more information about the problem and possible solutions.

2 comments

I think it depends on context.

If "Can we just <x>" is coming from a trusted colleague who understands the problem space that is exciting because they may have found a shortcut or clever solution.

If "Can we just <x>" is coming from a non-technical client or project manager then I feel nervous because in practice it often indicates that they have underestimated the scope of the problem or we have overestimated the scope of the problem. In some cases it is possible to have enough meetings to level-set expectations but in some cases the "just" seems to be a leading indicator of persistent project tension due to mismatched expectations.

I feel like "just" is a huge source of resentment between engineers and non-technical managers/clients/etc. Can we "just" return true if the picture contains a bird?[0]

[0] https://xkcd.com/1425/