DORA Metrics: How Engineering Teams Can Speak the Language of Executives

·1 views

DORA is a four-metric framework used to evaluate software delivery performance across two dimensions: throughput and stability. Deployment frequency and lead time for changes measure how fast teams ship, while change failure rate and time to restore service measure how reliably they do so. Research behind the framework challenges the common assumption that speed and stability are trade-offs, showing high-performing teams can achieve both simultaneously. Each metric translates directly into business outcomes — shorter lead times mean faster revenue, lower failure rates mean reduced firefighting costs, and higher deployment frequency enables more product experimentation. Experts recommend establishing a DORA baseline before building custom productivity dashboards, as its industry-wide recognition makes it easier to justify platform investments to leadership.

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)

GPU Cloud Cost Goes Beyond Hourly Rates, Reddit Data Shows

A GPU Cloud Research analysis of 80 evidence units drawn from 131 Reddit threads posted since January 2025 found that hourly pricing alone is a poor measure of true workload cost. Hidden expenses such as failed job retries, data transfer fees, persistent storage charges, and environment setup time can collectively exceed the base compute cost. In one reported case, a 10-minute GPU session was outweighed in cost by a 23GB data download, while other users lost hours of billable time to instance failures and repeated model downloads. The analysis argues that the more meaningful metric is the total cost of completing a workload successfully, not the per-hour GPU rate. Marketplace-style clouds may offer competitive pricing, but unreliable execution or recurring operational overhead can quickly erode those savings.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

One Commerce Protocol, Two Interfaces: Keeping AI and Human Actions Aligned

As AI agents gain the ability to perform commercial actions alongside human users, splitting the underlying transaction model between the two interfaces creates dangerous inconsistencies in state, permissions, and outcomes. The safer architectural approach is to build both a Progressive Web App (PWA) for humans and a Model Context Protocol (MCP) server for agents on top of a single shared state machine. Each interface handles what it does best — humans manage identity, review terms, and approve sensitive steps, while agents handle structured discovery, comparison, and request preparation. Authorization is made explicit through a capability matrix, where agent permissions must name specific actions and their boundaries rather than inheriting broad access from a credential. Irreversible or high-risk actions require live human approval via a Passkey ceremony in a browser, a protocol-level requirement that no agent scope declaration can override.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Shopify enables WebMCP agent tools by default across all Liquid storefronts

Shopify has quietly activated WebMCP tools by default for all standard Liquid storefronts and Hydrogen developer previews, requiring no installation or configuration from merchants. The move gives AI agents the ability to call real storefront functions — including product search, cart management, and checkout — rather than scraping page content. The tools operate within the shopper's live session and trigger the same storefront actions a human user would, keeping the existing theme behavior intact. However, the default setup only covers Shopify's built-in commerce actions; any custom features such as configurators, subscription managers, or B2B workflows must be manually registered to become agent-accessible. The rollout, coming shortly after Cloudflare made a similar move, signals that agent-ready infrastructure is becoming a platform-level default rather than an optional developer project.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Form 4 Insider Trade Filings Lag by 2 Days on Average, Up to 8.6 Years at Worst

An analysis of 10,951 SEC Form 4 insider trade filings from July 2026 found that the median delay between a transaction date and public dissemination on EDGAR is two days, though the gap can stretch to over eight years in extreme cases. While 92.9% of filings met the SEC's two-business-day deadline, roughly 4% arrived more than five calendar days late, and 110 filings were delayed beyond 90 days. Open-market purchase filings — the category most studied in insider-trading research — were the least punctual, with one in five missing the deadline window. By contrast, open-market sale filings were nearly always on time, likely due to streamlined broker-assisted paperwork pipelines. The study warns that financial backtests using transaction dates instead of filing dates risk look-ahead bias, effectively trading on information that was not yet publicly available.

0 comments Read more at DEV Community