3 ms·

Any efficiency gains which come from cleaner organization structure are gone because of the lossy translation mechanism between a PM and Eng team. You can argue

Any efficiency gains which come from cleaner organization structure are gone because of the lossy translation mechanism between a PM and Eng team. You can argue that good PMs translate requirements perfectly, but this is a rare skill and I’m just saying I’ve never seen it from someone in this role. Perceived enjoyment of one’s role is a separate topic, but not completely orthogonal. If someone just wants to code and they force them to be a PM then their personal productivity might drop. This is why I asserted in the beginning I’m talking about feature teams, where a role fit I described is more likely. As engineering becomes less expensive with generative models I can imagine efficiency tilts even further in favor of engineers doing more PM-like work.

LtWorf 1y ago
> As engineering becomes less expensive with generative models So, not in this decade?
crazygringo 1y ago
> You can argue that good PMs translate requirements perfectly, but this is a rare skill and I’m just saying I’ve never seen it You can also argue that good devs translate requirements into code perfectly with zero bugs, but it's also a rare skill and I've never seen that. Because in the real world, nobody's perfect. The good news is you don't need to be perfect to still add lots of value. Demanding a standard of perfection from others, that I would hazard to guess you do not meet yourself, is rather uncharitable.
- gregorygoc 1y ago
  For the right set of requirements I can fix bugs in my system with significantly less effort, than rewriting a system which was built with wrong assumptions to begin with. Again, wrong analogy. I don’t demand perfect analogies though. Treat this as rather charitable gesture.