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 →

Asaf Ezra 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 5 · Cm 4 4.85

Q So see, definitely power laws happening here, huh? Yeah. All right. Very good. What's the backstory? When did you launch the company?

A Uh, so we launched almost three years ago. Uh, we actually started completely differently. We started with, uh, load balancing opportunities. Uh, we've seen a huge, huge potential in the fact that load balancers today don't even have any knowledge of what happens on your backend system. Um, so you can think of gRPC or, uh, HTTP load balancing where, uh, Pretty much the only heuristics today is like, uh, least connection, or least outstanding requests, but the truth is, it doesn't mean how loaded the machine actually is, so how much the resources are utilized, and for what purpose, and so we started there. Unfortunately, it didn't go as planned. Uh, we realized that a lot of people are not very enthusiastic to replace their own very easy to use Infinitely scalable AWS backed load balancer. Um, so we switched to something else that you can start with a single VM, but the worst case, uh, um, and the cost benefit is like, I'm risking single VM with this unknown company, and I can gain 30, 40, 60%, uh, on my performance improvements.

AI assessment note: “we launched almost three years ago. Uh, we actually started completely differently.”

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.