3 ms·

I read this through a completely different lens. The people I've seen with this type of behaviour have been bitter or incompetent leads or managers. I too wishe

I read this through a completely different lens. The people I've seen with this type of behaviour have been bitter or incompetent leads or managers. I too wished they would take a long hike of a short bridge, but chose to leave the company instead. Entitled and demanding people who offered very little value and had built their careers by trampling on others. No thanks for me.

alexk307 5y ago
There are certainly exceptions to every case, but I when I was first starting out my career, I was super guilty of doing this. Always asking my coworkers for help or information, even though I had all the access to information that I needed, or could just ask Google. It wasn't until the lead engineer kindly sat me down and told me that I need to be more responsible for my interruptions and only ask when you're completely stumped. Some of the best career advice I have gotten in this industry.
- righttoolforjob 5y ago
  That is good advice! I got the same from my first manager: Research and try to find the answer first before reaching out for help. I had in fact already done that in the particular situation in which he commented, but he was right in principle anyway, so no harm done. I have a very different feeling about the OPs situation though. This is not about junior people asking too many questions or being lazy or incompetent, it is about a personality of people who are just entitled and demanding and just generally bitter assholes. Not typically seen in juniors!
- ajford 5y ago
  My last two positions have followed the exact opposite philosophy, and I prefer their take. The general consensus at these places was that getting to the information faster is preferable. We have a team chat channel for a reason, ask their. Don't stop your search, and don't ask first thing, but after a cursory glance, ask. Then continue to search on your own. If someone knows the answer and sees the question, they should respond. If you find the answer first, update the thread and answer your own question in case it helps anyone else. That said, I agree if the answer was easily found in a google search. That's the kind of basic info an engineer/developer should be able to answer on their own with research and self-exploration. It's key to be able to tell quickly whether the answer/info you're looking for is likely to be a common/general piece of info or a company/industry specific piece of knowledge that might not be found widely.

alexk307 5y ago

There are certainly exceptions to every case, but I when I was first starting out my career, I was super guilty of doing this. Always asking my coworkers for help or information, even though I had all the access to information that I needed, or could just ask Google. It wasn't until the lead engineer kindly sat me down and told me that I need to be more responsible for my interruptions and only ask when you're completely stumped. Some of the best career advice I have gotten in this industry.

righttoolforjob 5y ago
That is good advice! I got the same from my first manager: Research and try to find the answer first before reaching out for help. I had in fact already done that in the particular situation in which he commented, but he was right in principle anyway, so no harm done. I have a very different feeling about the OPs situation though. This is not about junior people asking too many questions or being lazy or incompetent, it is about a personality of people who are just entitled and demanding and just generally bitter assholes. Not typically seen in juniors!
ajford 5y ago
My last two positions have followed the exact opposite philosophy, and I prefer their take. The general consensus at these places was that getting to the information faster is preferable. We have a team chat channel for a reason, ask their. Don't stop your search, and don't ask first thing, but after a cursory glance, ask. Then continue to search on your own. If someone knows the answer and sees the question, they should respond. If you find the answer first, update the thread and answer your own question in case it helps anyone else. That said, I agree if the answer was easily found in a google search. That's the kind of basic info an engineer/developer should be able to answer on their own with research and self-exploration. It's key to be able to tell quickly whether the answer/info you're looking for is likely to be a common/general piece of info or a company/industry specific piece of knowledge that might not be found widely.