this post was submitted on 19 Jun 2023
21 points (88.9% liked)

Programming

17502 readers
22 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
21
How To Be An Engineer That PMs Don't Hate (blog.staysaasy.com)
submitted 1 year ago by nick to c/programming
2 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago

Another place that engineers can over-rely on PM is in project management. Because PMs are most active at the start and end of projects - handing the steering wheel to engineers to execute and picking it back up when code is complete to deliver downstream - there can often be blurriness about how much PMs should be project managing in the middle. The TLDR here is that PMs should not be running all project meetings. Engineering managers, IC project leads, or tech leads need to be managing engineering execution, not PMs.

Strong disagree. This drive by style of product manager is so disconnected from the delivery of the team, that the relationship borders on useless. I know product managers are adverse to doing what they see as project management but this particular style of product management leans too far into abstracting the product manager from the product that they are responsible for.

The best, most productive PMs I’ve worked with are part of the team delivering the software.