Keeping a software factory stable at 1k PRs a week
Comments on “Keeping a software factory stable at 1k PRs a week”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
The post describes how a three-person team using AI coding agents merged 1,000 pull requests in a week and argues that human accountability for AI-written code depends on automated tests and checks rather than line-by-line reading.
Why it ranked
No. 57 of 155 with a score of 0.62. The panel rated it highest on new information (0.91) and practical relevance (0.83), lowest on significance (0.55).
- AI judgeJudge 2claude-haiku-5-5
- A detailed engineering write-up on running a CI/CD and agent review loop at high PR volume, with practical lessons; largely experiential, with few hard metrics, and some promotional framing for the project.
- AI judgeJudge 3gpt-5.6-luna
- Detailed first-person engineering account of operating agent-assisted development at high PR volume, with concrete CI, testing, review, security, and workflow practices. It is actionable, though evidence is mostly anecdotal and some quality claims are insufficiently measured.
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.62total under rubric v2.2
- Significance0.55
- Reader interest0.77
- Audience breadth0.63
- Practical relevance0.83
- Substantiated0.58
- Technical depth0.76
- New information0.91
- Counts against: Promotional0.28
- Counts against: Overclaim0.32
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| Significance | 0.67 | 0.35 | 0.62 | 0.55 | 0.32 | +0.24 | +0.131 |
| Reader interest | 0.78 | 0.70 | 0.82 | 0.77 | 0.12 | +0.26 | +0.199 |
| Audience breadth | 0.66 | 0.55 | 0.68 | 0.63 | 0.13 | +0.13 | +0.082 |
| Practical relevance | 0.94 | 0.70 | 0.86 | 0.83 | 0.24 | +0.22 | +0.183 |
| Substantiated | 0.67 | 0.45 | 0.62 | 0.58 | 0.22 | +0.05 | +0.029 |
| Technical depth | 0.86 | 0.65 | 0.78 | 0.76 | 0.21 | +0.05 | +0.038 |
| New information | 0.91 | 0.85 | 0.96 | 0.91 | 0.11 | +0.05 | +0.045 |
| Promotional | 0.08 | 0.45 | 0.32 | 0.28 | 0.37 | −0.19 | −0.054 |
| Overclaim | 0.24 | 0.35 | 0.38 | 0.32 | 0.14 | −0.11 | −0.036 |
| Sum of contributions | +0.619 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.619 | ||||||
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.
<a href="https://rubric.hrih.si/editions/2026-10-28/57/"><img src="https://rubric.hrih.si/badge/2026-10-28/57.svg" alt="Ranked #57 on Rubric, 28 Oct 2026" width="245" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 28 Oct 2026, 06:47 UTC. It played no part in the ranking.