Claude Design

Isaac Asimov: The Last Question (1956)

Ban the sale of precise geolocation

Measuring Claude 4.7's tokenizer costs

Ada, its design, and the language that built the languages

NASA Force

Middle schooler finds coin from Troy in Berlin

Show HN: Smol machines – subsecond coldstart, portable virtual machines

All 12 moonwalkers had "lunar hay fever" from dust smelling like gunpowder (2018)

NIST gives up enriching most CVEs

Healthchecks.io now uses self-hosted object storage

Tesla tells HW3 owner to 'be patient' after 7 years of waiting for FSD

Iceye Open Data

Show HN: PanicLock – Close your MacBook lid disable TouchID –> password unlock

Hey HN! We&#x27;re Charles and Dean, and we&#x27;re building Stage: a code review tool that guides you through reading a PR step by step, instead of piecing together a giant diff.Here&#x27;s a demo video: <a href="https:&#x2F;&#x2F;www.tella.tv&#x2F;video&#x2F;stage-demo-1pph" rel="nofollow">https:&#x2F;&#x2F;www.tella.tv&#x2F;video&#x2F;stage-demo-1pph</a>.
You can play around with some example PRs here: <a href="https:&#x2F;&#x2F;stagereview.app&#x2F;explore">https:&#x2F;&#x2F;stagereview.app&#x2F;explore</a>.Teams are moving faster than ever with AI these days, but more and more engineers are merging changes that they don&#x27;t really understand. The bottleneck isn&#x27;t writing code anymore, it&#x27;s reviewing it.We&#x27;re two engineers who got frustrated with GitHub&#x27;s UI for code review. As coding agents took off, we saw our PR backlog pile up faster than we could handle. Not only that, the PRs themselves were getting larger and harder to understand, and we found ourselves spending most of our time trying to build a mental model of what a PR was actually doing.We built Stage to make reviewing a PR feel more like reading chapters of a book, not an unorganized set of paragraphs. We use it every day now, not just to review each other&#x27;s code but also our own, and at this point we can&#x27;t really imagine going back to the old GitHub UI.What Stage does: when a PR is opened, Stage groups the changes into small, logical &quot;chapters&quot;. These chapters get ordered in the way that makes most sense to read. For each chapter, Stage tells you what changed and specific things to double check. Once you review all the chapters, you&#x27;re done reviewing the PR.You can sign in to Stage with your GitHub account and everything is synced seamlessly (commenting, approving etc.) so it fits into the workflows you&#x27;re already used to.What we&#x27;re not building: a code review bot like CodeRabbit or Greptile. These tools are great for catching bugs (and we use them ourselves!) but at the end of the day humans are responsible for what gets shipped. It&#x27;s clear that reviewing code hasn&#x27;t scaled the same way that writing did, and they (we!) need better tooling to keep up with the onslaught of AI generated code, which is only going to grow.We&#x27;ve had a lot of fun building this and are excited to take it further. If you&#x27;re like us and are also tired of using GitHub for reviewing PRs, we&#x27;d love for you to try it out and tell us what you think!

HN