| I read it the exact opposite, that the engineer is just being difficult, especially with the last three: "I don't know who would read it. This will take too long. It feels like busy work." I mean, who do you think is going to read it? Obviously anyone who needs to interoperate with the service. And the first three parts, let's address in turn: "Well, I don't know what outline to use." Whatever outline other documentation at the company uses. "I don't know how to publish it." So ask somebody who has published documentation how they do that. "I don't know what content I should add." Look at pre-existing documentation and use that as a model. I mean, this isn't rocket science here. This is clearly somebody obstructing things -- somebody who doesn't want to be a team player. If, as an engineer, you can figure out how to set up git to make a commit, you can figure out how to publish documentation. It's entirely inappropriate to be using up your manager's time asking them to hand-hold you through this, when you can just ask a fellow team member to send you the resources you need. This isn't elementary school -- it's a professional work environment where you've been hired for your expertise and your ability and initiative to solve basic daily problems on your own. The dialog as presented does portray the engineer as either lazy or incompetent, no question about it. |