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 →

Edith Harbaugh no published score: only 1 usable exchange 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
1on raw tape
0redirected or not addressed
Answered raw tape D 4 · C 4 · P 4 · Cm 4 4.00

Q week and want the most intense cultures. And on the other hand, I think during lockdown, a lot of folks worked even less. Maybe a lot of, a lot of folks started working 15:20 hours a week. Um, so what have you learned on that journey to a hundred, and how to, how to make that work? And, but be competitive, because you had to win in a competitive category.

A Yeah, well, thank you, Jason. Um, so I think my intent was, ah, so I'd, I'd been in startup since the dot-com era, and I'd been that person that worked, you know, 80, 90 hours a week. I remember sleeping under my desk, because the bar had shut, and it's, it's not sustainable. Um, it leads to a lot of burnout. It leads to people just not doing their best work is the other thing. Ah, I learned that, you know, I was working more hours, and I would come back and look at my work the next day, and I had made so many mistakes. You know, I was, um, in engineering at the time, and I did some work that ended up getting patented, which is great. So, clean technical writing was really key. And if I was like in this brain fog, I wasn't doing great work. And the other thing that would happen is if you get a bunch of snippy people who are working on little sleep, they start getting very snippy with each other. Um, so it's, it's not a productive environment. You think that you're working more, you're really getting less done. Uh, so what we were trying to build was this thing where you could do your best work. Uh, and definitely there were some weeks where we were working 80, 90 hours, but those were kind of these peaks and valleys of, like, um, you know, I talked about how we did the Microsoft Build Conference. You know, at the time we were an eight-person company, so all the engineers, like,…

AI assessment note: “what we were trying to build was this thing where you could do your best work”

page 1
Made with StarZero

Turn any episode into a week of clips.

This entire site, over 400 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.