Unfortunately this is true; and if you're not careful with your time, a lot can be wasted by people who realize "I can email so-and-so instead of putting in 5 minutes to finding the issue myself".
replyThey're usually pretty courteous in their interaction, which makes it all the more difficult to be "rude", in my case, by adding an exponential falloff in response times - after I realize what's happening, I tend to take a little longer for each reply so they figure out it's faster to just do the research on their own most times.
> after I realize what's happening, I tend to take a little longer for each reply so they figure out it's faster to just do the research on their own most times.
replyAgreed, and I do the same. They still get a courteous reply, but they also feel a little "pain" when they don't get a timely answer - an effective teacher.
But as a good manager, you should throw it back: "what do you think?" "what have you tried so far?" etc.
replyJust giving them AI back is pointless. It means _your_ role is pointless.
Indeed - I had a team that called this "remote brain execution" (we were a build team that used Bazel, and often fielded questions about why someone's build broke).
replyMy favorite phrase on that team was "What have you tried so far?"
Ironically, I have to edit out my "what I have tried so far" when asking questions, because I'm more likely to go into a long-winded explanation of the headers that I hacked and the kernel module I installed to fake my way around this or that, when the actual answer tends to be "uh... are you sure you're building the code you think you are? That sounds like you're running from the wrong directory or wrong branch."
replyNot just the workforce, my parents still barely know how to use a computer because any time they hit the slightest snag, they immediately call me for help.
reply