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 →

Daniel Hauschildt 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 it's, it's not representative of the business, right? The average is just total revenue divided by customers. So that's your average, but what you're saying is very different. Yeah. You have very, you have very different profiles of people. Um, okay. So, so again, tell us more of the backstory here. So you launched the, you actually had your first paying customer in 2017 or you started writing the code?

A Our summer, way around two to 16, we had started writing the code, um, basically, and we actually wrote it not for sale in the beginning. Actually, we were part of our bigger software agency, digital agency, and we were having different, let's say customers, which we figured out needed something like photo editing in their applications. But to be honest, they were not willing to pay the amount of money it would take to build it really, right? And so, and we started building it ourselves, more like a side project, and then said, okay, you can just have it in your, in your product, but it was not, let's say, the sum you would pay if you develop it one time. So this is how we really started, and then we really put it on GitHub back then, um, seeing if somebody might, might use it, and eventually we thought maybe it's just an open source tool and people will be happy about it, but, um, then things changed quickly.

AI assessment note: “around two to 16, we had started writing the code”

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.