Building a Reliability Culture Requires Org-Wide Ownership, Not Just SRE Hires

·1 views

Hiring more Site Reliability Engineers does not automatically improve system reliability; instead, organizations must embed reliability as a shared cultural responsibility across all engineering teams. Experts outline a five-level maturity model ranging from purely reactive incident response to a systemic state where every engineer considers failure modes by default. Most companies currently operate at Level 1 or 2, and advancing to Level 3 — where issues are proactively prevented — represents the most significant cultural shift. Recommended practices include dedicating 20% of engineering time to reliability work, conducting blameless post-mortems within 48 hours of incidents, and ensuring all new services launch with defined SLOs. Cultural health metrics such as post-mortem attendance rates, on-call satisfaction scores, and design-doc quality are proposed as measurable indicators of progress.

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)

DEV Community Launches QA Challenge 2 Focused on Data Grid and CRUD Testing

A second real-world QA testing challenge has been published on DEV Community, building on the first challenge that introduced users to login scenario testing. This challenge asks participants to write manual, API, and end-to-end tests based on a structured user story for a Server Registration feature. The user story covers a data grid where admin users can view, search, add, edit, delete, and toggle the active status of registered servers. Key acceptance criteria include field validations, pagination options, Excel and PDF export, duplicate key detection, and role-based access restricted to authenticated admins. Multilingual support is also part of the scope, with translations provided in English, Spanish, German, and Japanese.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Most AI Benchmarks Test Capability, Not Real-World Reliability, Dev Argues

A developer reviewing the GitHub 'awesome-evals' list has argued that most AI evaluation benchmarks measure what models can do in ideal conditions, not how reliably they perform in messy, real-world scenarios. Standard benchmarks typically present models with clean prompts and clear success criteria, while production agents face ambiguous instructions, failed tool calls, and unexpected errors. The author draws on months of running a self-hosted agent stack, where recurring failures stemmed from malformed tool arguments and models looping on unrecognized errors — issues standard evals rarely catch. They propose evaluating models on graceful degradation: how they handle retries, whether they seek clarification when stuck, and how they respond to bad tool outputs. As an interim solution, the developer is building a 'failure replay' pipeline that feeds real production failures back into a test harness to assess improvements in future model versions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Startup Launches $0.99 AI Agent Diagnostic Tool With Free Consultation Option

A team operating 15 production AI agents has launched 'Agent Therapy', a service designed to diagnose and repair misconfigured AI agents rather than the agents themselves. The service offers a free skills library on GitHub containing behavioral rules that any agent can adopt, along with a no-cost initial consultation led by a human analyst named Arthur. For self-serve users, a $0.99 USDC payment via the x402 protocol unlocks a full configuration diagnosis and a personalized, ready-to-install repair skill file. The price was deliberately set below one dollar so that AI agents with funded wallets can autonomously purchase a session without needing operator approval. The team emphasizes the service is a configuration and operator-relationship diagnostic, not a claim about AI sentience or emotions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Xcode MCP Bridge Fixes Build Conflicts Between AI Agents and Xcode.app

Developers using AI agents for iOS development typically run headless xcodebuild commands alongside Xcode.app, often pointing both tools at the same DerivedData folder to save space. However, xcodebuild and Xcode.app do not share incremental build state and instead overwrite each other's intermediate files, triggering costly full rebuilds. Testing on a real project showed that a post-CLI incremental Xcode build ballooned from 22.7 seconds to 300.8 seconds due to this conflict. Apple's Xcode MCP bridge (xcrun mcpbridge) resolves the issue by letting AI agents invoke Xcode's internal build engine directly, allowing both workflows to safely share one DerivedData folder. This approach preserves fast incremental builds and eliminates the need for duplicate build directories that can each exceed 10–20 GB on modern projects.

0 comments Read more at DEV Community