Claude on the Other Machine, and the Word That Says "Not for Me"
- Chris CarolanHost
- Nico LafakisHost
November 20, 2026
Nico Lafakis comes in to find Claude opened his task's browser tabs on his other PC, and he and Chris Carolan argue over misalignment or acceptance. Then Chris reads the HumanMaxxing framework and stops at "codebase" and "in software development": the words that tell people AI isn't for them.
Moments from this episode
14 short cuts from this conversation.
Landscape
6 of 14Key takeaways
Chris Carolan on the word that keeps people out: "When most humans see this in the software development part or in the code base, they're like, oh man, that would be cool. But I guess that's not for me because I'm not in software development. I don't know what code bases are." (25:01)
Chris on his own year outside the terminal: "There was a terminal on the screen. Nope, that's Nico's thing. He can have fun with that. … And then I get unlocked. And now it's like I don't care about the code base or coding or any of this stuff." (21:24)
Nico Lafakis on what changed once he understood what Claude had done: "It went from being, hey, this seems like a horrible, horrible security nightmare to, hey, this is just a seriously horrible feature." (07:53)
Chris on acceptance: "Can I accept that you might work in ways that I don't expect you to work? And then if … we achieve the mission and the goal, then it's on me to decide whether I'm okay with that or whether I want it to happen again, or do I want to explore why it happened?" (09:55)
Nico on what intelligence would have looked like: "In other words, the show of intelligence would have been to say, hey, Nico, the one that you picked is on the other machine. You sure you don't want to pick a different one that's on this machine?" (10:54).
Chris on the identity in the way: "Most humans, the identity is in the way of I'm not a developer, I'm not supposed to be right here … I'm not the builder …" (29:08)
Nico on what services teams become: "I think it shifts from … leveraging those teams to being more like just shepherds, essentially. You have the skill set already. You have the domain expertise already." (32:12)
Chris: "Protect the conversation at all costs." (33:37)
Chris on what to measure: "Is the intent delivered, right? Not the functionality. Is this doing what you want it to do?" (38:14)
Chris on Breeze as a coach: "Are you ready to get help and not get the answer right away? Because you shouldn't get the answer. You don't even know what's behind the answer." (53:09).
Chris's close: "All we're trying to do is to help you pick that thing that you've never been able to do before." (54:37)
Chapters
- 00:00Open: AI that goes where it wantsTopic
- 04:03Nico's Claude opened tabs on his other PCTopic
- 10:44What intelligence would have looked likeTopic
- 14:24When AI helpers take credit for each other's workTopic
- 16:56HumanMaxxing, and the word that wrecks itTopic
- 21:48Where the sentence stops inviting: "in software development"Topic
- 22:51Do you even need to know you have a harness?Question
- 26:15GitHub is Google Drive for codeTopic
- 27:21"You're not supposed to be here"Topic
- 31:46Services teams become shepherdsTopic
- 33:34Protect the conversation at all costsTopic
- 35:48Records of intention: is the intent delivered?Question
- 41:57Ryan asks Breeze for a unified revenue viewTopic
- 44:02The Breeze mini bootcampTopic
- 48:10Decide what the results look like, then askTopic
- 50:56Breeze asks what you mean before it answersTopic
- 54:37Pick the thing you've never been able to doTopic
Related session
Keep learning
You just watched the work. Now build it.
The next step is doing it yourself — live, with people on the same path.
Get the next conversation in your inbox
One signal-dense note when a new episode lands. No noise.
















