The Exchanges

Every argument clarity score on this site is built from rows on this page. Each question and answer was assessed with names hidden, the host's own answers included, on four things from 1 to 5: directness (does it answer the question asked), coherence (do the ideas follow), precision (concrete details and clear references), compression (says a lot per word). The weighted mix (30/30/25/15) is the exchange score. A person's published score averages their exchange scores on raw tape only, at least 8 of them, shrunk toward the cohort mean. Full method →

Adam Sabin no published score: no usable exchanges on raw tape, and a fair score needs 8+ record → ← everyone

Every exchange below was scored with names hidden, four dimensions each from 1 to 5. An exchange's score is 0.30·directness + 0.30·coherence + 0.25·precision + 0.15·compression. The published score averages the raw tape exchange scores and shrinks small samples toward the cohort mean, so five great answers can't beat twenty good ones. Produced feed rows count only toward coarse estimates, never toward a full score.

clear all ✕
1exchanges match
0on raw tape
0redirected or not addressed
Answered produced feed D 5 · C 5 · P 4 · Cm 4 4.60

Q And that's, uh, there's a lot of people that ask me, they go, Nathan, how are these people on your show launching these extremely efficient dev teams in India, especially when one of the founders is not from India or, you know, Kiev, Ukraine, or there's places in Argentina. How did you spin up your India team?

A I'm really lucky. Our, one of our early engineers was a guy named Niden. Um, very well experienced, and he was our, our first, he was a full-time engineer for us. Um, and he just, I mean, that's actually funny. He said, hey, I've got a, I actually have a brother who's also looking for a job. I can definitely vouch for him. All of a sudden, we had Niden to cash two brothers. Um, and next thing we knew it, we were making trips out there. Um, We knew they had the capability to, to lead and build a team out there. So, uh, yeah, I think the key thing is, is having two people that you really trust, know what quality looks like. And then my CTO makes trips out there. He knows what good code looks like and the rest follows.

AI assessment note: “one of our early engineers was a guy named Niden”

page 1
Made with StarZero

Turn any episode into a week of clips.

This entire site, over 2,600 episodes transcribed, diarized, checked and made playable, runs on the StarZero media pipeline. Drop in your own episode and the podcast clipper finds the moments worth sharing, cuts them, captions them, and reframes them for every feed.