Why AI PR review time claims like Atlassian's 45% may not apply to your team

·14 views

Vendors like Atlassian cite impressive figures — such as a 45% reduction in pull request cycle time using their Rovo tool — but these are self-reported metrics with no control groups or reproducible methodology. A DEV Community analysis warns that aggregate averages can be misleading, as AI tools often speed up small, simple PRs while larger, complex changes remain slow or get slower. Teams are advised to measure their own before-and-after results using a fixed time window, the same reviewer pool, and comparisons split by PR size and risk level. Tracking tail metrics like p90 and p95 cycle times is recommended over relying solely on mean figures, which can mask regressions. Reviewer workload is another overlooked factor — if engineers spend more time reading AI-generated comments than they saved on reviews, the cycle-time improvement is effectively illusory.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Mixture of Experts: How Sparse Routing Scales Model Size Without Matching Compute Costs

Dense transformers spend the same compute on every parameter for every token, so making them larger also makes them more expensive. Mixture of Experts (MoE) instead keeps a large pool of parameters but activates only a small subset for each token. A learned router scores the experts and selects the top few, so total model size can grow far faster than per-token cost. This design introduces a risk: the router can concentrate traffic on a few experts while others go unused, a problem typically countered with an auxiliary load balancing loss. The article explains the routing mechanics, why balancing matters, and when MoE may be the wrong architectural choice.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Microsoft Offers Voluntary Exits to About 60,000 Eligible Employees

Microsoft announced a Voluntary Exit Offer on October 26, 2026, covering eligible employees at level 70 and below in Canada, India, the United Kingdom, and the United States. Participation varies by organization, and the program includes financial support and career-planning resources. Reuters reported that roughly 60,000 employees are eligible, though the offer is voluntary and does not mean that many people have already been dismissed. Microsoft has not linked the departures to automation or AI, describing the move instead as adapting its workforce to changing needs. The eligible group also includes employees who are not developers.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

A 28-day Search Console review: 1,510 impressions but only 6 clicks for a new site

A small English-language site of about 70 posts, aimed at foreigners handling everyday matters in China, examined its 28-day Search Console data after impressions rose sharply over roughly two weeks. Most impressions came from pages already ranking in the top 10, yet those pages drew only 5 clicks from 1,131 impressions, a click-through rate under half a percent. The author attributes the gap largely to weak titles and descriptions that read as topic labels rather than answers to the questions users actually search. Query-level data was incomplete because Search Console applies privacy thresholds at low volume, so the page-level view was used instead. The author's planned response is to rework titles and descriptions rather than publish more posts.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

pgbrake: an undo layer for Postgres when AI agents run SQL

The developer describes pgbrake, an open-source MCP server that lets AI coding agents such as Claude Code and Codex work against Postgres databases without direct access. Each statement is parsed with pglast, and before UPDATE or DELETE operations the affected rows are saved locally so they can be restored with an undo command, which refuses if those rows changed afterward. DDL, statements without WHERE clauses, and changes touching more than 100 rows require human approval through the client or a terminal command that cannot run without a TTY. All statements and decisions are recorded in a local audit log, and nothing leaves the user's machine. The tool is MIT-licensed, written in Python, and has been tested only on Postgres 17, with its author noting that undo does not cover TRUNCATE or DDL and is no substitute for backups.

0 comments Read more at DEV Community