Press Space to continue
Press Space to continue
A PM shipping pull requests is usually just noise to engineering. Pavneet, PM for infrastructure at Together AI, says that directly, and the rest of his demo is about what makes it not true in his case. His split is clean. Defining the feature, the API surface area, the abstraction layer. All human, all hands on. The code writing is the part that runs on its own. Decisions stay with him, execution does not. Then the mechanism that makes execution safe to hand over. They maintain a full…
Aakash Gupta@aakashgupta3d ago
Together AI just raised $800M at an $8.3B valuation. I got their product team to open up the actual repo they run on: 0:00 - Slop is the new party foul 1:44 - Why individual output backfired 3:26 - Inside the shared product repo 8:57 - Who owns the context files 10:41 - Team skills vs personal skills 11:57 - Picking a harness and a model 15:17 - Feature research running live 16:57 - What stays human in the loop 19:56 - The PRD skill that interviews you 23:09 - Half a day of research in 5 min 24:25 - Their customer insights MCP 27:31 - What a good PRD looks like now 32:02 - Reading the finished PRD 35:07 - Every repo in one place 40:24 - Context is a hierarchy, not a pool 41:20 - Build your own orchestrator 44:19 - Agent evals on shipped features 49:41 - Design validated every few hours 52:26 - Where PM ends, engineer begins 55:10 - What it actually cost them
View
