|
|
|
|
|
by Rule35
1905 days ago
|
|
It depends. Sometimes the answer is obscure because of our setup - like you'd need to know to look in the other repo. I'll always tell you that, and point you to the doc and the problem-list to update in case the doc is wrong. But, if you ask me a question where the answer is in the code, the proper answer you seek, in the detail you need, then I'm going to ask you to read the code first and only ask me what's left. Perhaps the story is true as retold, or maybe the original guy asked about the right things and read the code for the rest, but people watching from the outside couldn't tell and conflated it all, turning it into a story of ladder-pulling bitterness. That doesn't really ring true for me because I want coworkers taking responsibility for these odd systems (that they have to find me to ask about). But I don't want to be stuck in the role of their System-X guy who they get to do their changes. This guy's incentive would be to walk the line, educate and hand-off. |
|