3 ms·
The article makes a fair point, but if the promotion being denied to the "glue" is one that should be doing lots of coding, then it doesn't make sense to promot
by ineedasername 8y ago
The article makes a fair point, but if the promotion being denied to the "glue" is one that should be doing lots of coding, then it doesn't make sense to promote the glue.
It doesn't matter that the glue was performing the most high-impact tasks at the moment, they were tasks that generally fall into the project manager/product lead category. If these activities are tending to fall onto people in SE roles, that probably means the organization is too lite on project manager roles, or they aren't properly aligned with and/or integrated with the SE teams, and that is the bigger issue that needs to be addressed.
Otherwise, If an organization is self-aware enough to recognize the "glue" issue to begin with, then it should be self aware enough that an SE doesn't have to become glue. The SE can raise the issue with management that they need more PM activity to coordinate glue tasks.
- majormajor 8y agoHanding off technical coordination and leadership to PMs is a recipe for problems, IME. A TPM isn't going to spot that two different other engineers have different mental models of the proposed specs. A TPM isn't going to spot the edge cases that could turn into future bugs without carefully revisiting the design. A TPM isn't going to put your rollout plan together so all the services do all the things in the right order. I've seen organizations that will tell you, when you reach a certain point as an individual contributor, that "they aren't paying you just to code anymore," and that covers a fair amount of "glue." And that "you don't want a PM/TPM doing it" thing is covered in the linked article to, but it fits what I've seen, male or female. The PMs and TPMs I've worked with were not deep in the code of the projects they were working on, so it would be impossible for them to be technically deep enough to do all that glue work. You need someone putting engineer-level time into engineer-level stuff. I'll let my TPMs and PMs run down a lot of other stuff for me, but not the detailed engineering problems. That's my responsibility as an engineer, not something I can offload just because it's "not coding." Which takes me back to saying you should foster - and promote - well-rounded "not just coder" engineers.
- ineedasername 8y agoYou're absolutely right, but the article cites many examples of tasks that are properly within the PM domain. And for those that aren't, it should be the SE team &/or management dictating that such responsibilities be shared rather than devolve onto a single individual. A single individual taking it on themselves is self-defeating. It keeps the organization dysfunctional at the same time that the individual is ignoring a significant chunk of assigned duties (coding)