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 →

Rich Waldron 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 5 · C 4 · P 4 · Cm 4 4.30

Q Thank you very much. How, um, technically minded does one need to be to do this? Um, not in theory, but I guess across your user base are those people that just know nothing about tech that can do this?

A Yeah, good question. It's typically people that, uh, you know, have no understanding of technology or don't use tools in any way and are really not suitable for a platform like Trey. Um, there's sort of a broad base from your engineer that really doesn't want to be the person that gets lumbered with having to solve the integration headache and will have their code tied to them for next time it needs to be fixed, um, within the team that they've been called into through to where we see the sweet spot, which is that ops type, It's, it's, as I kind of described earlier, somebody that understands logic is, is, um, used to moving data around and understanding kind of the hows and whys behind it. Typically we see people that are quants or, um, particularly useful with spreadsheets and can build heavy Excel models are a really good tray user. On our backend, uh, we actually have built our own scoring models, which will detect dependent on The types of workflows that you're trying to build, and the way you use the product, we assign a score which helps us determine how complex you are, how technical you are, and how much, sort of, support to provide in application, and where to take you next in the, in the product.

AI assessment note: “have no understanding of technology or don't use tools in any way and are really not suitable”

page 1
Made with StarZero

Turn any episode into a week of clips.

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