Edition of Friday 20 November 2026

Design for Understandability

Comments on “Design for Understandability”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Jonathan Schuster, in a talk given at Google's internal Code Health Summit in November 2025, argues that as LLMs write more code, engineers' main job shifts to reading and judging it, so systems should be designed for understandability, as they were once designed for testability. He proposes three practices: design by contract, data invariants, and isolating side effects and global state, all aimed at local reasoning. The claims are argued from examples and experience, not measured, and several lack cited sources.

Read the original at jschuster.org. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 13 of 140 with a score of 0.67. The panel rated it highest on new information (0.86) and practical relevance (0.85), lowest on substantiated (0.41). The judges disagreed most on substantiated (spread 0.40), so the story is marked contested. Placed No. 13, No. 20 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
A thoughtful opinion talk on software design practices (contracts, invariants, side effects) with practical advice relevant to builders, though it cites little evidence and is conceptual rather than novel or landmark.
AI judgeJudge 3gpt-5.6-luna
A substantive, practical software-engineering talk connecting contracts, invariants, effects, and local reasoning to AI-assisted development. It offers useful guidance but little empirical evidence and somewhat overstates universal understandability goals.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.67total under rubric v2.3Contestedjudges differ by 0.40 on substantiated

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.55
  • Reader interest0.75
  • Audience breadth0.85
  • Practical relevance0.85
  • Substantiated0.41
  • Technical depth0.68
  • New information0.86
  • Counts against: Promotional0.05
  • Counts against: Overclaim0.35

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.630.450.580.550.18+0.24+0.133
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.630.800.820.750.19+0.26+0.195
Audience breadthHow many people who build technology does it concern?0.920.800.820.850.12+0.13+0.110
Practical relevanceHow useful is it to someone who builds software or tech products?0.910.800.840.850.11+0.22+0.187
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.220.400.620.410.40 , above the contested threshold+0.05+0.021
Technical depthHow technically substantive is it?0.760.600.680.680.16+0.05+0.034
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.900.700.970.860.27+0.05+0.043
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.070.050.030.050.04−0.19−0.010
OverclaimDo the headline or conclusions claim more than the body supports?0.430.200.420.350.23−0.11−0.038
Sum of contributions+0.674
Claim-check penalty0.000
Total, as published0.674

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #13 on Rubric, 20 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-20/13/"><img src="https://rubric.hrih.si/badge/2026-11-20/13.svg" alt="Ranked #13 on Rubric, 20 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenQuote

    Google's Code Health guide says that for code to be sustainable it must be understood, and that key components of code health include good documentation, easy to understand error messages, and clear, simple code.

    The article gives no link or citation for it.

    The article says

    “For code to be sustainable, it must be understood”

    The source says

    No source to compare with.

  2. No source givenCausal conclusion

    A decade or two ago, the software industry thought writing multiple tests for every public method in an API was infeasible because code was not designed for testability; practices later changed.

    The article gives no link or citation for it.

    The article says

    “a decade or two ago, we used to think that writing multiple tests for every public method in an API would have been infeasible”

    The source says

    No source to compare with.

  3. No source givenGeneralization

    Today, designing code for testability is so ingrained in software culture that doing anything else is practically unthinkable.

    The article gives no link or citation for it.

    The article says

    “Today, designing our code for testability is so ingrained into our culture that doing anything else is practically unthinkable”

    The source says

    No source to compare with.

  4. No source givenCausal conclusion

    Protos give completely uncontrolled access to the underlying data representation, so they are poorly suited to ruling out certain states.

    The article gives no link or citation for it.

    The article says

    “Protos give you completely uncontrolled access to the underlying representation of your data”

    The source says

    No source to compare with.

  5. No source givenCausal conclusion

    Hidden inputs and outputs (side effects and dependencies on global state) make code hard to test, hard to reuse, and hard to reason about.

    The article gives no link or citation for it.

    The article says

    “They make code hard to test, hard to reuse, and hard to reason about”

    The source says

    No source to compare with.

  6. No source givenCausal conclusion

    With Design by Contract, a developer can verify a method by reading only the contracts of the methods it calls, not their code.

    The article gives no link or citation for it.

    The article says

    “we can read just the contract on those called methods, not the code”

    The source says

    No source to compare with.

  7. No source givenGeneralization

    The Monarch team at Google used group programming sessions to apply Design by Contract, and it worked well for them.

    The article gives no link or citation for it.

    The article says

    “The Monarch team at Google did this with their Design by Contract practice and it worked well for them”

    The source says

    No source to compare with.

  8. No source givenCausal conclusion

    Local reasoning keeps the needed context small, which benefits LLMs because context costs limited tokens.

    The article gives no link or citation for it.

    The article says

    “contexts costs tokens, and your tokens are limited. So LLMs give us another great motivation to use local reasoning and minimize our context”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 3 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 20 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Design for Understandability”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.69

    Inkling 2 Mini