---
title: "Comment by Indie Ship Log on \"Code Review Starts with What Must Stay True\" | Hashnode"
description: "The stock allocation example is the one that stuck with me. A fix that keeps the count right but shuffles display order looks clean in a diff and still breaks a"
url: "https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4/comment/6adf01c5da89bc08440b9beb"
---

[Discussion](https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4)

Comment [Code Review Starts with What Must Stay True](https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4)

[Indie Ship Log](https://hashnode.com/@indieshiplog)

[Oct 26](https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4/comment/6adf01c5da89bc08440b9beb)

The stock allocation example is the one that stuck with me. A fix that keeps the count right but shuffles display order looks clean in a diff and still breaks a quiet invariant. Writing those two laws down before the review would have caught it faster than another pass over names. I am going to try one or two must-stay-true lines at the top of my own PRs, even when I am the only reviewer.

[Hiroyuki Nakahata](https://hashnode.com/@iroha1203)

[Oct 26](https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4/comment/6adf01c5da89bc08440b9beb#reply-6adf522e2498241548ffadba)

Thanks for the comment! I agree. With AI writing code so quickly, I think it’s especially important to spell out the properties we want to preserve and check that they still hold.