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 →

Ion Stoica no published score: only 2 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 ✕
2exchanges match
2on raw tape
0redirected or not addressed
Answered raw tape D 5 · C 5 · P 5 · Cm 5 5.00

Q a question about that because one of the things that I've always thought about when it comes to this tension between academia and industry, you might hear about needs and requirements from industry, but when you're in research environment, you have unlimited open-ended, you know, vision and an algorithm and a research paper is very different than something in production at industry scale. So how do you guys navigate that?

A First of all, students, they do internships, they understand It's a problem. They develop the first solutions. And then with that understanding, you can start more principled designs to build these systems. But the truth is that in every successful project, we had at least one or two partners. For instance, uh, for, um, we work very closely initially with Facebook. When we started working with Facebook, Facebook, you know, has an entire, uh, cluster, big cluster for big data. It was 80 nodes. And their big data team was like three people. Then, for instance, in the case of Mesos, we work very closely with Twitter. And Hinman went to Twitter and worked very closely with Twitter engineer to deploy Mesos in production. And actually, the feedback from Twitter has a big impact on the Mesos evolution. From just supporting big data, cluster computing frameworks like Hadoop, it went to support These long running services.

AI assessment note: “worked very closely with Twitter engineer to deploy Mesos in production.”

Answered raw tape D 5 · C 5 · P 5 · Cm 4 4.85

Q a question about that because one of the things that I've always thought about when it comes to this tension between academia and industry, you might hear about needs and requirements from industry, but when you're in research environment, you have unlimited open-ended, you know, vision and an algorithm and a research paper is very different than something in production at industry scale. So how do you guys navigate that?

A First of all, students, they do internships, they understand It's a problem. They develop the first solutions. And then with that understanding, you can start more principled designs to build these systems. But the truth is that in every successful project, we had at least one or two partners. For instance, uh, for, um, we work very closely initially with Facebook. When we started working with Facebook, Facebook, you know, has an entire, uh, cluster, big cluster for big data. It was 80 nodes. And their big data team was like three people. Then, for instance, in the case of Mesos, we work very closely with Twitter. And Hinman went to Twitter and worked very closely with Twitter engineer to deploy Mesos in production. And actually, the feedback from Twitter has a big impact on the Mesos evolution. From just supporting big data, cluster computing frameworks like Hadoop, it went to support These long running services.

AI assessment note: “in every successful project, we had at least one or two partners.”

page 1
Made with StarZero

Turn any episode into a week of clips.

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