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 →
Jez Humble 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.
Answered produced feed
D 5 · C 5 · P 5 · Cm 4 4.85
Q So if you can't measure lines of code, what can you measure? Because I really want an answer, like how do you measure productivity?
A So velocity is the other classic example. Agile, there's this concept of velocity, which is the number of story points a team manages to complete In an iteration. So before the start of an iteration, in many Agile, particularly Scrum-based processes, you've got all this work to do. You're like, we need to build these five features. How long will this feature take? And the developers fight over it, and they're like, oh, it's five points. And then this one's going to take three points, this one's going to take two points. And so you have a list of all these features, and you don't get through all of them, but at the end of the iteration, the customer signs off, well, I'm accepting this one, this one's fine, this one's fine, this one's a hot mess, go back and do it again, whatever. The number of points you complete in the iteration is the velocity.
AI assessment note: “velocity is the other classic example. Agile, there's this concept of velocity”
Answered produced feed
D 5 · C 5 · P 5 · Cm 4 4.85
Q So if you can't measure lines of code, what can you measure? Because I really want an answer, like how do you measure productivity?
A So velocity is the other classic example. Agile, there's this concept of velocity, which is the number of story points a team manages to complete In an iteration. So before the start of an iteration, in many Agile, particularly Scrum-based processes, you've got all this work to do. You're like, we need to build these five features. How long will this feature take? And the developers fight over it, and they're like, oh, it's five points. And then this one's going to take three points, this one's going to take two points. And so you have a list of all these features, and you don't get through all of them, but at the end of the iteration, the customer signs off, well, I'm accepting this one, this one's fine, this one's fine, this one's a hot mess, go back and do it again, whatever. The number of points you complete in the iteration is the velocity.
AI assessment note: “velocity is the other classic example. Agile, there's this concept of velocity”
