@charliermarsh: For uv/ty/Ruff, I think the answer is kind of circular: as soon as reading the code stops revealing meaningful problems…
Summary
Charlie Marsh discusses the threshold for trusting AI-generated code in tools like uv and Ruff, suggesting that improvements in models, harnesses, and verification are needed before he stops manually reviewing the code.
View Cached Full Text
Cached at: 07/06/26, 12:06 PM
For uv/ty/Ruff, I think the answer is kind of circular: as soon as reading the code stops revealing meaningful problems. Likely solved by a mix of better models, better harnesses, better verification, and overcoming my own skill issues.
Theo - t3.gg (@theo): How much better do the models have to get before you’ll stop reading the code?
Similar Articles
When I reject AI code even if it works
The author explains why they often reject AI-generated code even when it works, citing reasons like inability to explain the approach, overly large diffs, premature abstractions, and reduced system reasoning, and argues for mandatory human review.
@svpino: If you are reviewing 100% of your AI-generated code by hand, you aren't moving fast enough. It's just impossible. Revie…
The tweet argues that manually reviewing all AI-generated code creates a bottleneck and links to a resource for a better approach.
How do you know when an AI coding agent is actually done?
The author built OpenPitStop, an open-source tool that independently checks and verifies the work of AI coding agents, demonstrated on a broken application, and invites discussion on how to trust AI changes.
@mstockton: Kind of. If by vibecoding you mean that they built a set of robust evals to prove their re-write was correct, and that …
A developer discusses how Anthropic's backend rewrite to Rust involved building robust evals and parallel-running systems to verify correctness, arguing that constraining non-deterministic AI tools is the key challenge in AI-assisted coding right now.
AI coding agent output verification in 2026: read the diff, vibe check it, merge
A reflection on current practices for verifying AI coding agent output, noting that developers often skim diffs and merge without fully auditing the agent's session activity, raising concerns about code review culture in the age of AI.