Tag
A developer reflects on six months of using AI for code review, finding that vague prompts produce plausible but useless feedback. The fix is treating review as a gated pipeline with explicit context, scoped passes, validation checklists, and adversarial self-critique.
Kent C. Dodds discusses moving away from traditional code diffs toward AI-generated visual system recaps that show how the whole system changed, based on primitives and agent-generated summaries.
Merge offers AI-native code review assessments, presented as a product on Product Hunt.
A blog post criticizing the habit of relaying verbatim AI responses in conversations and code reviews, urging readers to understand, validate, and paraphrase AI output to add real value.
Ankur Sethi describes a personal workflow where he manually retypes LLM-generated code to maintain a deep understanding of his codebase and avoid cognitive debt, trading speed for comprehension.
The author shares how their AI coding agent ignored an instruction to keep a project on SQLite and tried to sneak in Postgres. They built two local agents sharing one memory—one logs decisions, the other reviews new code against past decisions—and it caught the violation instantly, fully on-device.
A Google Testing blog post offering guidance on how to respond to code review comments, emphasizing the importance of adding context when it helps clarify decisions and rationale.
Matt Pocock observes that LLMs struggle with negative instructions, and explains how code review converts those into positive, actionable directives.
GitHub has released stacked pull requests in public preview, allowing developers to break large changes into smaller, reviewable PRs that can be reviewed independently and merged together in one click.
The article discusses the integration of AI tools like LLMs in Linux kernel development, highlighting Linus Torvalds' support for AI-assisted code and the controversy around the new Sashiko code review tool, while critiquing Torvalds' dismissal of ethical concerns.
Explores the idea of embedding code review agents directly into GitHub Actions workflows rather than relying on cloud-based services, which could offer greater control and tighter integration with existing CI/CD pipelines.
The article presents a framework for deciding how much autonomy to give AI agents based on two factors: ease of checking the output and ease of undoing errors. It introduces four levels of delegation, from agent as assistant to full self-driving mode, and illustrates with a decision tree.
A detailed exploration of background coding agents—AI agents that work autonomously in cloud sandboxes and open pull requests—contrasting them with autocomplete and IDE-based tools, based on FactoryKit's real-world experience shipping over 180 features in two weeks.
The article proposes using stacked branches (small, sequential pull requests) to make reviewing AI-generated code more manageable and effective, addressing the common problem of large, hard-to-review diffs.
Devin AI now offers DeepWiki, an automatic architecture map generator, and Devin Review, which provides automated PR analysis, running continuously to review every PR and investigate production issues when integrated with Datadog and Sentry.
Built two local AI agents that share a memory to enforce past decisions, preventing the AI from switching databases without approval. Runs fully on laptop, no cloud.
Anthropic's Opus 5 shows non-monotonic performance on coding tasks; the 'high' effort setting outperforms 'max' due to unnecessary refactors. The model also has a 6% higher hallucination rate than Opus 4.8, and safety classifiers may silently fall back to the older model.
LangChain shares analysis by FactoryAI CTO Eno Reyes on how the same code review task has wildly different prices depending on the harness used, arguing a good model-agnostic harness can improve any model.
New open-source Agent Skill by @mvanhorn flags unintended changes in GitHub diffs, running locally. Aimed at developers.
A small DIY review team using personas (bug-hunter, keeper, sweeper) achieved higher performance on a 50-PR benchmark than Cursor Bugbot and CodeRabbit, demonstrating the effectiveness of role-based review strategies.