5 ms·

You don't want me to have even a FEW HOURS to work out a difficult problem? That is utterly unreasonable. I think you are imagining only a certain kind of probl

You don't want me to have even a FEW HOURS to work out a difficult problem? That is utterly unreasonable. I think you are imagining only a certain kind of problem while ignoring many other kinds. It took me hours to work out how to make a lovely visualization using the Plotly library in Python. No one else knew how to use Plotly. I figured it out and gave them a demo. They are glad I went into the cave. Most of my work is doing blockbusting like that, not doing easy things. But certainly, if someone on the team knows something about the tech I'm researching, I check in with him.

HWR_14 4y ago
Spending hours learning something and sharing that knowledge is being a team player.
fzeroracer 4y ago
What you are talking about is something that only exists as the result of teamwork. We all rely on documentation, people asking questions, people giving answers and people working as a team. If you're working on rare things where you are the only expert on the team then yes, you can have the opportunity to go into full focus mode and hammer something out. And as the other poster said, sharing that knowledge after you've finished is part of being a team player. If you simply say 'I am an individual contributor, I turn in my work and then I'm done' that to me sounds like someone that's not interested in sharing knowledge.
- watwut 4y ago
  > If you're working on rare things where you are the only expert on the team then yes, You dont need to be ONLY expert on the team for the above. Other people knowing the same thing dont prevent your knowledge of the system. For the above, you need to have passing knowledge of the thing you work on. And you should have build that knowledge while doing previous taks. The situation in which majority if tasks is assigned to developer who has no clue about that area of the system, again and again, is unreasonable.

HWR_14 4y ago

Spending hours learning something and sharing that knowledge is being a team player.

fzeroracer 4y ago

What you are talking about is something that only exists as the result of teamwork. We all rely on documentation, people asking questions, people giving answers and people working as a team. If you're working on rare things where you are the only expert on the team then yes, you can have the opportunity to go into full focus mode and hammer something out. And as the other poster said, sharing that knowledge after you've finished is part of being a team player. If you simply say 'I am an individual contributor, I turn in my work and then I'm done' that to me sounds like someone that's not interested in sharing knowledge.

watwut 4y ago
> If you're working on rare things where you are the only expert on the team then yes, You dont need to be ONLY expert on the team for the above. Other people knowing the same thing dont prevent your knowledge of the system. For the above, you need to have passing knowledge of the thing you work on. And you should have build that knowledge while doing previous taks. The situation in which majority if tasks is assigned to developer who has no clue about that area of the system, again and again, is unreasonable.