I highly doubt you never ask questions that you could’ve looked up yourself. “Go Google it” translates to “this isn’t worth my time,” which is a pretty rude way to be.
What I'm trying to say is that the cost of answering the question might look like 30 seconds to the person asking.
What really happened is, you context switch, answer a mundane question, and now spend 30 minutes to get back to the mental state that you were in that made you productive
But sometimes it isn't worth my time. If I'm being asked something about what I'm working on, fair enough. If I'm being asked what a command-line switch for curl does (and that's not related to what I'm doing) the total cost is less to look at the docs, rather then asking me to look at the docs.
Not weighing my time and effort into the equation is rude on behalf of the asker.
Nobody said you must answer any and all questions sent your way or that everyone is allowed to dismiss the value of your time. We’re veering away from the original discussion here.
if they aren't presenting proof of doing research or they don't have the benefit of doubt (e.g. a new hire, etc.) they're being rude by not doing the research in the first place.
I’m sorry but nobody behaves this way. Nobody sits around in every conversation showing their homework/proving they tried to find an answer before asking somebody else. It is incredibly common to just ask somebody a question and expect an answer regardless if you could’ve looked up yourself.
It’s important to not make everybody do your research for you, but what you’re describing is not at all typical.
I'm not particularly sorry, but when I ask questions out of the blue over email or chat, I always explain what I've already tried. The two exceptions are when it's urgent, in which case I briefly explain the urgency ("prod is down did you deploy just now?"), or when it's part of an ongoing conversation.
If this is not typical for you, then you are surrounded by people who disrespect you and your time.
steelman, don't strawman. pushback on someone being rude by requesting something they could have looked up doesn't look like "let me google that for you" 95% of the time. it's far more likely to come out as "I'm not sure, honestly. I worked on X, but I didn't really need to get in to Y, so I'm not as familiar. Personally, I'd just do a google search, since I'm a little behind on that."
not rude. not implying anything about the questioner. still the general sentiment of "google it; that's not my job". if you admonish people as being "incredibly rude", you should be talking about things that people actually do with enough regularity to make the point worth making. that is pretty widely understood.
Sure, but asking someone something that should be easily answered in a few seconds is also rude.
Programming is an intense job, in that it takes a lot of focus and time to build up a mental model of what you're working on to make progress
I highly doubt you never ask questions that you could’ve looked up yourself. “Go Google it” translates to “this isn’t worth my time,” which is a pretty rude way to be.
What I'm trying to say is that the cost of answering the question might look like 30 seconds to the person asking.
What really happened is, you context switch, answer a mundane question, and now spend 30 minutes to get back to the mental state that you were in that made you productive
But sometimes it isn't worth my time. If I'm being asked something about what I'm working on, fair enough. If I'm being asked what a command-line switch for curl does (and that's not related to what I'm doing) the total cost is less to look at the docs, rather then asking me to look at the docs.
Not weighing my time and effort into the equation is rude on behalf of the asker.
Nobody said you must answer any and all questions sent your way or that everyone is allowed to dismiss the value of your time. We’re veering away from the original discussion here.
if they aren't presenting proof of doing research or they don't have the benefit of doubt (e.g. a new hire, etc.) they're being rude by not doing the research in the first place.
I’m sorry but nobody behaves this way. Nobody sits around in every conversation showing their homework/proving they tried to find an answer before asking somebody else. It is incredibly common to just ask somebody a question and expect an answer regardless if you could’ve looked up yourself.
It’s important to not make everybody do your research for you, but what you’re describing is not at all typical.
I'm not particularly sorry, but when I ask questions out of the blue over email or chat, I always explain what I've already tried. The two exceptions are when it's urgent, in which case I briefly explain the urgency ("prod is down did you deploy just now?"), or when it's part of an ongoing conversation.
If this is not typical for you, then you are surrounded by people who disrespect you and your time.
> I'm not particularly sorry
Yes that seems rather consistent with your attitude.
As for the rest, you are drastically narrowing the scope
It's not typical but it's how you should personally act.
You aren't going to be able to convince others to be upstanding coworkers that actually give a damn, but you can be that person yourself.
steelman, don't strawman. pushback on someone being rude by requesting something they could have looked up doesn't look like "let me google that for you" 95% of the time. it's far more likely to come out as "I'm not sure, honestly. I worked on X, but I didn't really need to get in to Y, so I'm not as familiar. Personally, I'd just do a google search, since I'm a little behind on that."
not rude. not implying anything about the questioner. still the general sentiment of "google it; that's not my job". if you admonish people as being "incredibly rude", you should be talking about things that people actually do with enough regularity to make the point worth making. that is pretty widely understood.