Here’s what got my attention this week — a short list of things I read and watched recently that felt worth pausing on, as a product leader.
TL;DR What you choose to build — and how small you keep the right team doing it — may matter more than ever.
1/ What to Vibe Code (and What Not To)
“The most important question in tech right now: what should you vibe code?
Vibe code your product. Buy everything else.”
— Elias Torres
Elias Torres (Drift Co-founder) weighed in on build vs. buy in the age of AI. If you can spin up a Calendly clone in a weekend, should you?
His answer: Only if scheduling is your product.
You can vibe code a URL shortener, a lightweight CRM, an Asana-style goals tool. But you pay somewhere — not always in dollars, often in mindshare. In a world where everyone is AI-assisted, prioritization compounds.
In response to this tweet by Naval ^, Saeed Khan wrote a post reminding us what PMs need to be strong at.
“Vibe coding is not a superpower… There are three ‘superpowers’ that Product Managers (and Product Leaders) should focus on. Discovery and Market Research. Clear and Intentional Strategy. Meaningful Differentiation.”
— Saeed Khan
I think his point is that AI lowers the cost of building, but it may not lower the cost of being wrong.
My take: Anyone vibe coding is doing discovery and strategy — implicitly or explicitly. Differentiation... not so much. We could all use some superpowers in that area.
By the way, vibe coding also will have huge implications on product design. In a recent conversation with Lenny Rachitsky, Jenny Wen (who leads design at Claude / Anthropic) shared how design is changing. She also pointed out how humans will continue to make key decisions (and be accountable for them).
