Scores by kind of claim
Each kind of claim is scored on its own, out of 100: the share that held up, with the range it likely falls in. Fewer resolved claims give a wider range.
-
Factual claims
Statements about the present or the past, checked against the record: did they hold up?
84 79 88 -
Predictions
Statements about events outside the person's control, checked once they fell due: did they come true?
Insufficient record: 2 predictions resolved, 5 needed for a score.
-
Promises
Commitments to the person's or organisation's own future action, with something to deliver: was it delivered?
Insufficient record: 3 promises resolved, 5 needed for a score.
-
Guidance
A company's own figures for its results over a period, checked against what it then reported.
Insufficient record: 1 guidance claim resolved, 5 needed for a score.
All types combined: 84 (likely 79 to 88, high confidence), from 90 claims: 90 factual claims. It mixes kinds of claim in different proportions for different people, so compare people kind by kind.
Jeff Bezos's claims
35 claims
“For example, to construct a product detail page for a customer visiting Amazon.com, our software calls on between 200 and 300 services to present a highly personalized experience for that customer.”
Jeff Bezos, CEO, in shareholder letter 2011 2010 Letter to Shareholders (SEC (Amazon))
Building a product detail page on Amazon.com calls on between 200 and 300 services.
Mostly true True in substance, wrong in a detail.
The second judge would not resolve this claim; the verdict shown is the first judge's.
Said for an organisation they lead or work for; it counts on both records.
What would count as true or false
Judged as of the 2010 letter (published 2011). True: Amazon technical sources from around then (e.g., Werner Vogels's statements, or Amazon architecture papers) state that rendering a product detail page called on between 200 and 300 services, or a figure in that range. Mostly true: a contemporaneous figure is close to the range (e.g., 'over 100', 'up to about 150', or about 300 or more), describing the same page. Mixed: sources give a substantially different figure, or one for a different page or process. Mostly false: the figure is only loosely supported, e.g. from a much earlier period. False: credible technical sources show a count far outside the range (e.g., a few dozen).
Evidence
- Dynamo: Amazon's Highly Available Key-value Store Amazon.com authors (DeCandia, Hastorun, Jampani, Kakulapati, Lakshman, Pilchin, Sivasubramanian, Vosshall, Vogels), hosted on Princeton course site Own record
“For example a page request to one of the e-commerce sites typically requires the rendering engine to construct its response by sending requests to over 150 services.”
- Amazon Architecture - High Scalability - High Scalability (Todd Hoff blog) · 18 September 2007
“Between 100-150 services are accessed to build a page.”
Reasoning
The Dynamo paper by Amazon engineers, including Werner Vogels [E2], says a page request to one of the e-commerce sites typically sends requests to "over 150 services". A 2007 independent architecture write-up [E3] reports that "between 100-150 services are accessed to build a page." The High Scalability figure dates from 2007, about three years before the 2010 letter; the Dynamo paper is undated in the material. They are close to the claimed 200–300 range but below it, which matches the criteria's description of "mostly true" (e.g., "up to about 150"). Neither source gives a figure in the 200–300 range specifically for a product detail page.
Cite this claim
Jeff Bezos, “Building a product detail page on Amazon.com calls on between 200 and 300 services.” (said 2011). Verdict: mostly true. Reliability API, claim c_2b6bc3ef8054, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_2b6bc3ef8054
Claims without a verdict
Is a verdict here wrong, or do you speak for Jeff Bezos? Reply on the claim's own page, with the form at its foot (how replies work). Verdicts are made automatically; how verdicts and scores are made.