Same. That's way worse. For technical problems where an obvious and easy solution comes to mind, I'm fine saying something like "just" and fine with having it said to me. I'm expecting to either hear why the obvious solution won't work (learning more about the problem) or, less likely, give them help by pointing out something easy they happened to not think of.
"I'm really struggling to set up external authorization for the /download endpoint."
"Why don't you just use @external on it?"
Hopefully leads to either
"This endpoint needs to...[extra constraints]."
"Ah, gotcha."
or, less likely
"There's an @external?"
"Yeah, let me show you."
There are some differences between this and questions like "Why don't you just go for a walk to stop feeling depressed?". Maybe the biggest difference is these tech solutions are not paradoxical. Someone's depression may be defined by their inability to do something like go for a walk and enjoy it. Suggesting they do that is not helpful.
The questions are also more sincere. Like, I literally want to know why you're not doing the easy solution. I'm actually assuming that there's a good reason, like some extra constraint. That's why am I asking "why not?" instead of speaking in the imperative.
There's also a critical difference of the offered solution being much easier than the one attempted, or very easy overall. I might say "Why don't you just sort it alphabetically?" but I wouldn't say "Why don't you just make a DSL?".
I guess it's just that I think it's okay to act like something is small when you really believe it is for the person you're speaking with.
"I'm really struggling to set up external authorization for the /download endpoint."
"Why don't you just use @external on it?"
Hopefully leads to either
"This endpoint needs to...[extra constraints]."
"Ah, gotcha."
or, less likely
"There's an @external?"
"Yeah, let me show you."
There are some differences between this and questions like "Why don't you just go for a walk to stop feeling depressed?". Maybe the biggest difference is these tech solutions are not paradoxical. Someone's depression may be defined by their inability to do something like go for a walk and enjoy it. Suggesting they do that is not helpful.
The questions are also more sincere. Like, I literally want to know why you're not doing the easy solution. I'm actually assuming that there's a good reason, like some extra constraint. That's why am I asking "why not?" instead of speaking in the imperative.
There's also a critical difference of the offered solution being much easier than the one attempted, or very easy overall. I might say "Why don't you just sort it alphabetically?" but I wouldn't say "Why don't you just make a DSL?".
I guess it's just that I think it's okay to act like something is small when you really believe it is for the person you're speaking with.