Hey, at least he had the right idea. He saw that the delay was due to a lack of skilled workers and tried to fix that problem instead of just talking more about the project. That's more awareness than most PMs have in my experience.

[–] Maalus@lemmy.world 34 points 6 months ago

If a PM has enough time to try to learn programming on the side, then they are a shit PM. A PM should shield the team from unneccessary meetings, be the main initial contact point and the initial refinement guy. Those are 4 seperate jobs at once.

[–] KevonLooney@lemm.ee 17 points 6 months ago (2 children)

PMs act that way because people above them ask for updates regularly. Bad PMs don't know how to push back. If you need things done faster, the answer is usually "we need more resources".

[–] TheBat@lemmy.world 10 points 6 months ago

If you need things done faster, the answer is usually "we need more resources".

Like having 9 women to make a baby in a month?

[–] SolarMech@slrpnk.net 8 points 6 months ago (1 children)

"we need more resources" is bounded by the rate at which you can incorporate new teams members without absolutely destroying your productivity, or having a bunch of untrained fools running around breaking things (of course the later is standard at many places already, so I guess it doesn't always matter).

The right answer is usually : "No". Or at least "Prioritize". Or "This is what we need to get it done" at which point they might start to get software takes time to make decently, and they don't want software that doesn't work decently in the first place.

[–] Aceticon@lemmy.world 5 points 6 months ago

"Sure! You just have to choose which of these other things you want deprioritized since we're already going at full tilt"