Edition of Sunday 1 November 2026

Kotlin Flow: Bugs That Look Correct at First

Comments on “Kotlin Flow: Bugs That Look Correct at First”

3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked

The article walks through four common Kotlin Flow bugs that look correct at first glance: cold flows re-running upstream work per collector (fixed with shareIn), catch only handling upstream exceptions (not downstream ones), conflate() silently dropping intermediate values, and stateIn() with SharingStarted.WhileSubscribed never starting upstream without a subscriber, which matters…

Read the original at kt.academy. 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. 54 of 59 with a score of 0.56. The panel rated it highest on new information (0.92) and practical relevance (0.76), lowest on significance (0.38). Placed No. 54, No. 56 by score alone: the 13th Programming & dev tools story of the day (−0.080). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Practical Kotlin coroutines tutorial on common Flow pitfalls; useful to Android/Kotlin developers, well-explained with fixes, but modest significance and no novel research or recent-news overlap.
AI judgeJudge 3gpt-5.6-luna
A practical Kotlin Flow tutorial explaining cold streams, exception scope, conflation, and stateIn subscription behavior with runnable examples. Useful to Android developers, but narrowly scoped and not deeply novel or independently evidenced.

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.56total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.38
  • Reader interest0.58
  • Audience breadth0.46
  • Practical relevance0.76
  • Substantiated0.58
  • Technical depth0.70
  • New information0.92
  • Counts against: Promotional0.03
  • Counts against: Overclaim0.12

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.500.250.380.380.25+0.24+0.090
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.510.600.620.580.11+0.26+0.150
Audience breadthHow many people who build technology does it concern?0.520.500.350.460.17+0.13+0.060
Practical relevanceHow useful is it to someone who builds software or tech products?0.870.700.720.760.17+0.22+0.168
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.660.450.620.580.21+0.05+0.029
Technical depthHow technically substantive is it?0.930.600.580.700.34+0.05+0.035
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.910.900.960.920.06+0.05+0.046
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.040.050.010.030.04−0.19−0.006
OverclaimDo the headline or conclusions claim more than the body supports?0.170.150.040.120.13−0.11−0.013
Sum of contributions+0.558
Claim-check penalty0.000
Total, as published0.558

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 #54 on Rubric, 1 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-01/54/"><img src="https://rubric.hrih.si/badge/2026-11-01/54.svg" alt="Ranked #54 on Rubric, 1 Nov 2026" width="238" height="28"></a>

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 1 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 1 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 “Kotlin Flow: Bugs That Look Correct at First”

More on Rubric

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

  1. Score 0.79

    Zlib 1.4