Most of them don't read the code! And like not all PMs are engineers and most don't need to be, but even nontech PMs should be able to recite the architecture IMO. At GS many simply couldn't, and it made explaining project sizing very difficult without resorting to hand waving
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Yeah and of course this sort of stuff is gonna be product specific, like when I was working in consumer webapps I think I felt a lot differently about this stuff because it was more about UX design and persona research/customer segmentation than the tech.
Like different products call for different PMs, I defo don't want to advocate that all PMs need to code because they don't, probably more crtitical that they can articulate the revenue model for the product. But I think in most cases it helps and builds trust with the eng team
-
-
This Tweet is unavailable.
-
In my exp, PMs I've had in the past who were technically inclined were more of an ally bc I could push back on deadlines etc and they'd understand and help me to get priorities straight and convey complexities to mgmt. Don't need to code at all, just understand the parts
- Show replies
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.