I think the point of the article was that to be valuable as an engineer you have to do things like "making tough decisions, dealing with stakeholders, incomplete and poorly conceived requirements". My problem is that a lot of people have your attitude and pretend that they are doing me a favour by having this being written down all the while limiting the actual design space for a problem, and in the same breath patronise me on what teamwork is really like.
If you want to do that work, have you looked for ways you could get involved?
Or if it’s the case that you’re actually doing that work behind the scenes because the output from the PMs isn’t very useful, have you looked for ways to make your contribution more visible?
Comments
I think the point of the article was that to be valuable as an engineer you have to do things like "making tough decisions, dealing with stakeholders, incomplete and poorly conceived requirements". My problem is that a lot of people have your attitude and pretend that they are doing me a favour by having this being written down all the while limiting the actual design space for a problem, and in the same breath patronise me on what teamwork is really like.
If you want to do that work, have you looked for ways you could get involved?
Or if it’s the case that you’re actually doing that work behind the scenes because the output from the PMs isn’t very useful, have you looked for ways to make your contribution more visible?