this post was submitted on 09 May 2024
1256 points (99.3% liked)
Programmer Humor
19511 readers
319 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
"Are you don't yet? Why aren't you done yet? Help me update infinite plans that will be outdated in a week. Also, I just promised a bunch of stuff... all that stuff we already promised, I think you can do that faster."
When I was a dev, I once had a PM with no technical skills that decided he would "learn to program to help catch us up"... He did not succeed.
Yes, I am don't work here anymore, good bye.
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.
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.
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".
Calling people “resources” and the mindset that delivery teams are just a number that you can spend money to increase is a mark of poor project and personnel management, as well.
Like having 9 women to make a baby in a month?
"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.
"Sure! You just have to choose which of these other things you want deprioritized since we're already going at full tilt"