My take on vibe coding for PMs

Source: Hacker News

PMs shouldn’t waste time landing prod diffs at Meta scale

• If the feature is actually important, fix the system for prioritization (your real job) rather than circumventing it.
• You probably code like a slow E3 but cost the company an IC7 salary.
• It is very easy to accumulate tech debt with random PM pet features. Remember that even diffs to intern tools can break prod!
• You are friends with all the senior TLs, so can get them to review your code, but this is not a high‑leverage use of time.
• PMs landing prod features is generally snacking and mistaking motion for progress (flex on LinkedIn but don’t land any real prod impact).

Why should PMs code?

• Better communicate the idea/feature: showing is usually better than telling.
• Understand the systems: prioritizing and communicating with engineers is far easier if you have some sense of how your thing is built.
• Run more realistic experiments with human volunteers: mocks and UXR studies with static prototypes are dead.
• Temporally flex unique resources: leverage unique talent that you have as a PM, e.g. deeply understanding of an API built by your previous company.
• Fun!!!!!

What should all PMs do in AI independent of coding?

• Build EVALS!!!