Write broken commits for better review

kept by eddie apr 17

Separating mechanical from non-mechanical changes across intentionally broken commits, then squash-merging them, makes code review easier without cluttering history.

You should use AI for reviewing code especially when the diff is huge – Simian Words
Human reviewers should focus on offering out-of-distribution knowledge (context, design decisions) rather than line-by-line checks, which AI can handle.
also on #code-review, #software-engineering, #productivity, #developer-tools
Using AI to write better code more slowly
Using multiple LLMs for rigorous code review and bug finding can produce higher-quality code than the common fast-output approach, though it slows development velocity.
also on #code-review, #software-engineering, #productivity, #developer-tools