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 →

Christopher Nguyen 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 3 · C 4 · P 4 · Cm 4 3.70

Q So if you think of the arbitrage between technology and, I guess, almost a social engineering that's required for people to, Ask the right questions that machine learning and deep learning can solve in the enterprise. What, what, what's your, what's your take on this? What's the, when you go and sell to a company, do you feel that people know how to harness the power of what you're offering?

A Um, I, I, I guess I understand that question as, um, the, the way we approach business users at Aremo is that we actually respect them a lot. Uh, some people build software that say, you know, let's dumb them down. Uh, in fact, business users are very sophisticated people. They just speak a different language. Um, so earlier we had a discussion about the, the challenge of the business user having a lot of business rules in their head, and yet they can't translate them to SQL. So one of the things we do, like, you can imagine we do a lot of things under the hood in terms of technology. We actually split the ETL process both cognitively as well as technologically into two parts. One we call EETL, and the other we call BETL. EETL is Enterprise ETL, and BETL is Business ETL. And essentially we provide tools for people to, the EETL is essentially responsible for data structures. Converting a timestamp into Monday, you know, Tuesday, and so on. Whereas the business user should expect that the data set is already come, already well structured, but they will then easily from that impose business rules on it. And by, by separating these variables, you can essentially have that collaboration between data engineering and, and, and business quite, done quite smoothly. So you saw some examples of the ability to do that, because when I do that demo, if you think a little bit, you say, well, …

AI assessment note: “by separating these variables, you can essentially have that collaboration between data engineering and”

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.