> yet I assume you can distinguish good development practices from bad
Uh. We're not talking about knowing what good is, which is completely irrelevant to anything in this thread. You made a claim without qualification about what it is more likely for PMs to do. I can't tell if you've lost the chain or are engaging in some kind of motte and bailey fallacy. Either way it's a bad sign for this conversation.
I'm going to summarize the threads so far. I hope it highlights why what you've said sounds so silly:
Someone: "I see X failing to do Y."
You: "X definitely do Y. Why would you think that X aren't doing Y? Doing Y is the obvious thing for X to do."
Someone: "I literally am seeing it happen right now."
You: "Well then those X are bad."
Someone: "Yeah, no shit. They just said as much."
You: "But most X would do Y."
Someone: "In my experience that is false."
Someone else: "Mine too."
Someone else: "Mine as well."
Someone else: "Same."
You: "The bad ones shouldn't have their jobs."
Someone: "They do though."
You: "But we can tell which ones are the bad ones."
Someone: "Bartender, another drink please."
It is X with a given attribute of "good," not all X; thinking it is all members of X is what you are missing here. Most good PMs would review tickets, by definition. That bad ones do not is irrelevant to the argument, so it doesn't matter how many someone elses notice their PMs are bad, like yeah, no shit.
Anyway this is delving into pedantry deriving from the fact that you seem to have missed what I had said above, rather than engaging with what is going on with regards to PM productivity itself. Have a good day.