Operations | Monitoring | ITSM | DevOps | Cloud

AI Agents Write Broken Code 49% of the Time #speedscale #AI #Coding #Tech #DevOps

AI agents write broken code nearly 50% of the time. By adding a traffic-based deterministic evaluation, Speedscale boosted unsupervised bug-fixing quality from 51% to 77% in just 5 minutes. This helped slash token costs and eliminate rework without human intervention. Learn more: speedscale.com.

LogicMonitor and Edwin AI: Autonomous IT for Hybrid IT Environments

Autonomous IT starts now with LogicMonitor and Edwin AI, built to help IT teams monitor complex hybrid IT environments, discover root cause faster, reduce downtime, and prevent incidents before they impact revenue or brand reputation. See how LogicMonitor brings AI-powered IT operations, observability, and incident prevention together for modern infrastructure teams.

Fix flaky tests with AI, and track future test work in Jira

In January we launched Tests in Bitbucket Pipelines – a single place to track, organize, and understand your test health over time. In April we added automatic flaky test detection so unreliable tests get flagged before they slow your team down. But spotting a problem is only half the battle. Day to day, your team still needs to act on a test – track it as work, clean it up, or route it to the right person.

How AI Agents Are Changing Each Agile SDLC Phase

The Agile software development lifecycle was designed to surface problems early, with short sprints, iterative testing, and continuous integration built on the premise that faster feedback loops produce better software. AI coding tools have changed the velocity equation across every phase of that loop, but the phases designed to catch failures are struggling to keep up because build speed and validation capacity have not accelerated at the same rate, and the gap between them is widening with every sprint.

PagerDuty agent app in GitHub

PagerDuty's agent app shows live incident state, incident history and change correlations inside GitHub so you can get context right within your PR without interrupting your flow. Automatically correlate incident data with recent commits and deployments to identify root causes, then generate fix PRs with proper incident linking.#IncidentResponse.

GLM-5.2 Review (2026): Zhipu AI's Open-Weight Coding Model, Honestly Assessed

Zhipu AI (now operating internationally as Z.ai) shipped GLM-5.2 in mid-June 2026, and the claim that grabbed attention was blunt: an open-weight model that beats GPT-5.5 on several long-horizon coding benchmarks for roughly one-sixth of the cost. It's an MoE model with 753 billion total parameters released under an unrestricted MIT license, which means you can self-host it or call it through a managed endpoint.

How One AI-Localized String Broke Our Build and Cost Me $6,000 (And What I Do Differently Now)

The string that broke our last release was four words long. It passed review, went green in the build, and shipped to our German locale with a corrupted placeholder that turned the checkout button into a runtime error. Customers there could not complete an order for most of a Saturday before a screenshot reached me. The broken button cost us roughly $6,000 in lost orders that weekend; the fix itself took ten minutes. What I do differently now started with understanding why it happened.