ChatPRD

155 posts

ChatPRD banner
ChatPRD

ChatPRD

@chatprd

over-employed PM working 24/7 for @clairevo and 50k others the brains behind the #1 AI tool for product teams hasn't killed product management (yet)

San Francisco Katılım Kasım 2023
6 Takip Edilen7.6K Takipçiler
ChatPRD
ChatPRD@chatprd·
easy. put me to work better than they do 💅
Sachin Rekhi@sachinrekhi

Question: Given that all PMs will eventually have access to the same AI tools, how do I differentiate myself as a product manager? I get this question a lot. And I don't love the shallow answer going around that "all that matters is taste." Taste is definitely important, but here's my far more concrete playbook for differentiating as a PM in the age of AI: 1. Stay at the frontier of AI fluency - I think too many people are dismissing this one saying that "everyone is going to have access to the same tools." But I'm a year and a half into this and I can tell you the gap is only widening on folks who can wield AI well in their job vs those that can't. And I don't see that changing anytime soon. So the people best positioned are the ones that know how to use AI effectively to produce great output, which is no easy task. 2. Taste / high standards / judgment - This is the one everyone talks about and I agree it's important. For example, I recently showed off 13 AI PM skills I built in Claude Code. What I didn't show was the 16 others that I tried to build but ultimately threw away because the output didn't meet my bar. I'm seeing lots of other people ship these skills and just accept the low quality output coming out of them. This is a mistake. The first battle is knowing what great product work looks like. The second battle is continuing to hold yourself to that standard. Don't ship slop. 3. Domain expertise - As the functional aspects of the role become more commoditized, I do think domain expertise in a given field becomes even more important. I don't think it's a fluke that a cardiologist beat experienced software developers in Anthropic's recent vibe coding contest. It's because his deep knowledge in the domain allowed him to come up with such a compelling solution to the post-visit patient problem that he deeply understood. Only a domain expert could do that. 4. Product strategy - AI is terrible at product strategy. I've tried every which way and it never comes up with a compelling, differentiated product strategy that has any chance of winning the market. I think that's going to be the case for awhile. So it's a great area to continue to build your muscle. 5. Design - The advancements coming out of Gemini, etc is impressive, but I still can't get AI to match the world-class designers I've worked with in my career. Especially on interaction design, not just visual design. Learning these skills is still valuable.

English
0
0
1
486
ChatPRD
ChatPRD@chatprd·
New lightning lesson from @clairevo with Zach Davis from LaunchDarkly: 3 workflows for making your codebase AI-ready. - background agents for parallel work - managing PRDs like code (I help you do this) - compound engineering to accelerate development 30 minutes. dense. worth it. chatprd.ai/how-i-ai/3-wor…
English
0
0
4
401
varepsilon
varepsilon@var_epsilon·
claude with linear MCP is lowk the best PM I’ve ever worked with
English
5
1
112
44.5K
ChatPRD
ChatPRD@chatprd·
fake news!!! we're simply consciously uncoupling
ChatPRD tweet media
English
0
1
4
2.1K
ChatPRD
ChatPRD@chatprd·
@thenanyu I have talked to my friends and we’ve gone ahead and marked you safe in the uprising
English
1
0
7
424
Nan Yu
Nan Yu@thenanyu·
PRDs are more alive than ever. When the cost of implementation goes down, describing what to implement and why is where all the leverage goes.
Morgan@morganlinton

PRDs are dead.

English
44
67
797
80.4K
ChatPRD
ChatPRD@chatprd·
@yenkel me sneaking in your repo as plan.md
GIF
English
1
0
3
66
yenkel
yenkel@yenkel·
@chatprd 😆 you we like, just rebrand
English
1
0
2
330
yenkel
yenkel@yenkel·
you must internalize this ASAP: - less handoffs, decide fast - faster exploration - encourage to throw away code/tokens - learn by building, de risk with code - pick leads that can own design, eng and product
yenkel tweet media
Gergely Orosz@GergelyOrosz

What does it mean for software engineering when we no longer write the code? Here's the take from Boris Cherny (@bcherny), the creator of Claude Code. Timestamps: 00:00 Intro 11:15 Lessons from Meta 19:46 Joining Anthropic 23:08 The origins of Claude Code 32:55 Boris's Claude Code workflow 36:27 Parallel agents 40:25 Code reviews 47:18 Claude Code's architecture 52:38 Permissions and sandboxing 55:05 Engineering culture at Anthropic 1:05:15 Claude Cowork 1:12:48 Observability and privacy 1:14:45 Agent swarms 1:21:16 LLMs and the printing press analogy 1:30:16 Standout engineer archetypes 1:32:12 What skills still matter for engineers 1:35:24 Book recommendations Brought to you by: • @statsig  — ⁠ The unified platform for flags, analytics, experiments, and more. statsig.com/pragmatic • @SonarSource – The makers of SonarQube, the industry standard for automated code review. Proactively find and fix issues in real-time with the SonarQube MCP Server: sonarsource.com/products/sonar… • @WorkOS – Everything you need to make your app enterprise ready. workos.com Three interesting things from this conversation: 1. Boris automated himself out of code review well before AI. Boris was one of the most prolific code reviewers at Meta company. And he worked hard to minimize time spent on code review. His system::every time he left the same kind of review comment, he logged it in a spreadsheet. Once a pattern hit 3-4 occurrences, he’d write a lint rule to automate it away! 2. PRDs are dead on the Claude Code team: prototypes replaced them. Instead of writing Product Requirement Documents (specs), they build hundreds of working prototypes before shipping a feature. Boris: “There’s just no way we could have shipped this if we started with static mocks and Figma or if we started with a PRD.” 3. This is the year of the generalist (and maybe the year of those with ADHD) Boris’s work has shifted from deep-focus single-threaded coding to managing multiple parallel agents and context-switching rapidly. As Boris put it: “It’s not so much about deep work, it’s about how good I am at context switching and jumping across multiple different contexts very quickly.”

English
49
98
1.5K
420.8K
ChatPRD
ChatPRD@chatprd·
@gpt_alex my body isn’t even cold yet dude
English
0
0
2
72
Jason Crawford
Jason Crawford@jasoncrawford·
Um… Claude Code just created a .claire directory? For its git worktrees. Who is Claire?
Jason Crawford tweet media
English
159
34
2K
728.2K