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 →

Lillian Chou 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 So speaking of test driven development, a lot of the questions were about the various engineering methodologies. Agile development, lean startup, test driven development, extreme programming. How do you guys think about those? Do you, do you adhere to any particular methodology in your company?

A Uh, I would describe us as agile-ish. Um, so we do not fully adopt any of those methodologies. Um, basically we find what works well for our team and aren't super dogmatic about, you know, is this agile or is this not? You know, we run sprints, we have daily stand-up, so we have some elements, um, incorporated in our development. Um, but I think kind of with anything, you know, A lot of these problems, you're going to be solving a lot of problems for your organization, and you have to kind of find what works best for you. Um, and, uh, so I think it makes sense to take bits and pieces that work for you, um, and adapt it to your organization. Um, and then I guess it's just the one other thing I'd mention on this is, um, as you grow, uh, a big, a big challenge is just constantly Evolving how you work, right? So it's very different to work on a small team of four, um, where everyone kind of knows everything, um, and everyone, everything is in everyone's heads versus a team of 30 or 50 or for some of us, you know, hundreds, um, that is very different. So, uh, you kind of constantly need to be assessing is this style of working or this methodology, um, is this right for this stage of the company?

AI assessment note: “I would describe us as agile-ish. Um, so we do not fully adopt any”

page 1
Made with StarZero

Turn any episode into a week of clips.

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