Tessl stops code review, shifts to intent verification
The story so far
Tessl stopped line-by-line code review and shifted to validating intent before code generation. The merged PR volume of the team is four times that of last year and almost all AI-generated, making review a bottleneck. The team shifted to reviewing acceptance criteria, constraints, and edge cases, and transformed repetitive review comments into machine-executable rules (invariants), thereby shifting the focus of review from the code itself to decisions and rule ownership.
AI-written from the reports · Updated 27 days ago
Coverage timeline
Follow the coverage to see every side of the story.
- Tessl BlogWe stopped reviewing code and started verifying intent
Tessl Blog stops line-by-line code review and starts verifying intent. The team's merged PR volume is four times that of last year and almost all AI-generated, making review a bottleneck. The team shifts to reviewing intent before code generation (acceptance criteria, constraints, and edge cases), and transforms repetitive review comments into machine-executable rules (invariants), thus shifting the focus of review from the code itself to decision-making and rule ownership.