Been having too much fun with GPT-Realtime-2 in the API, not just for fun personal things, but for really elegant complex voice interactions in @chatprd
Why type when you can talk?
I tried to kill PM, but @AnthropicAI is hiring more of them.
Why?
Because engineering is getting massive AI leverage and the PM capacity cannot catch up. Even with standard ratios (1 PM: ~5 engineers) it feels more like 1 PM to 20 engineers.
Interesting that the response is both a) hire more PMs (which says that PMs are at max capacity/leverage) and my more favorite tool -> b) turning engineers into PMs
This is my fave use case of @chatprd - I see so many teams deciding "anyone can cook" and using the app to make non PMs a little more product-minded...without the meetings.
What I really want to see though is what we can build to get those PMs the same 4-5x leverage that the engineers are getting. So far PMs are still
- managing stakeholders
- getting everyone to agree
- spending time with customers
- playing with the right solution via prototypes
Are these things that AI can eventually replace?
My bet is yes, but until then... apply for those anthropic jobs 😎
"PR >> PRD"
Yep. the handoff era is over. but it's not just the roles collapsing. it's the tools.
Every PM tool was built for a world where humans did the coordination.
tickets
docs
roadmaps
presentations
all of that was scaffolding for work AI now does faster and cheaper. slapping AI on top doesn't fix it. The foundation is already out of date.
I build @chatprd every day knowing i have to replace its core before something else does: claude code, another startup, something i haven't imagined yet.
Radical humility and endless paranoia are the only product strategies that make sense right now.
So sure. the PRD is dead.
But I'll kill it before you do.
I’ve spent at least 100 hours setting up, training, and working with @openclaw
Read the docs. Peeked into the source code. Edited config files by hand. Walked friends though their setup.
Then, I wrote down everything I know.
Here it is: The Ultimate 0 > 🦞 Guide
ty ty to @lennysan@nateliason@davemorin@steipete@lindsmccallum@elawless for early feedback.
gl hf snap snap 🦞https://t.co/McmguuljrN
I’ve seen this floating around, most people ick-ing at this as Claude derangement syndrome.
But guess what! This CEO probably just wants to get great outcomes fast, and I’d bet he’s thrilled to hear something other than “it’s not a priority” or “let me revise this and we’ll come back next week” or “thanks for the input but we have experts on the team.” Maybe your team isn’t producing work up to their standards. Maybe your company is slumping along at single digit or negative growth and the board has said it’s up or out. Maybe he’s trying to drive up AI adoption. Maybe the CEO job sucks and AI makes it more fun. Maybe AI raises the floor and the ceiling on everything.
I will say I’d rather a CEO who cares about driving up quality of marketing copy than one that’s checked out. I’d rather be lead by a Claude Boi than an exec team that forms a “AI innovation committee” and is just starting their limited 2 quarter trial of copilot. I’d rather just have the answer handy “yep, we did deep research on this via ChatGPT and figured out how to automate brand assets consistently thought nano banana, do you have any feedback?”
SLOP ENGINES BEWARE for sure, but I generally think folks don’t have enough insight into how corporate anxieties and power dynamics make the exec job a lonely one, and I’m not surprised CEOs are reaching for tools that shorten feedback cycles, openly brainstorm, and produces work (not more meetings.)
Look. Do I think there are better styles of leadership? For sure.
Do I think that means some teams don’t need a major wake-up call? No.
Ok have fun. Tell Claude hi.
Let me tell you what I LOVE about running @chatprd — I am forced to stay on the knife’s edge of what’s coming. Cancellations start to tick up citing Claude Code? OK - we need to rethink of agent strategy. No longer completing against chatGPT, but in house builds? Cool, what can I imagine that’s better.
Bootstrapped, no excuses, no delusions.
Hard but WORTH IT.
I’m not gonna bet against Claude Code, but there is a very important lesson in product competition going on right now, and it’s this:
The features ≠ the Product
New blog post: "A sufficiently detailed spec is code"
I wrote this because I was tired of people claiming that the future of agentic coding is thoughtful specification work. As I show in the post, the reality devolves into slop pseudocode
https://t.co/V86V7cjWpS