This is good. I really like intellectual (vs. emotional) disagreement on the intertubes because it opens eyes to new viewpoints.
Too bad Bex is wrong.
He’s not really. I just wanted to write that.
Anyway, we’re not that far apart; it’s really a glass half full/half empty perspective difference. In this case, I’d say I’m representing the half full glass, which is out-of-the-ordinary for me, and it’s more like 80% full.
Meaning, it’s generally useful for product management to know how to code; it’s a should-have, not a must-have or a nice-to-have.
If you encounter the 20% that Bex discusses, you’ll definitely remember the negative experience, which makes sense.
As with anything, balance is key, and breadth of knowledge doesn’t hurt either. A PM who is too functional can lead to unusable or impossible to build software that needs to be redesigned by development (or other PMs), and a PM who is too technical can lead to design without empathy, one of my latest kicks.
Happy medium is happy.
Again, as with many arguments, there are corner cases. This is 80/20 stuff.
Anyway, add your thoughts there or here.