Read what ships.

01GitLab · tutorial

PHP2Shell: GitLab helps find and remediate critical PHP flaws

Critical remote code execution vulnerabilities known as PHP2Shell affect the PHP engine across multiple versions, requiring immediate runtime updates to fixed versions or patched distribution packages. The team utilized platform features like container scanning, code search, and automated agent workflows to locate PHP projects and remediate vulnerabilities. Operators must also check logs and environments for signs of compromise as framework updates and input validations cannot prevent these engine-level flaws.

DEPTH ■■■■■10 min read3 days ago

ArchitectureSecurity

Sign in to save and rate

02GitHub · architecture

The bridge to agent-scale Git infrastructure

GitHub faced infrastructure capacity limits and a 25ms cross-region network round trip when migrating repositories to Azure. The team changed the storage quorum from repository-wide locks to per-reference serialization and introduced ephemeral virtual replicas backed by object storage. This raised write throughput, prevented slow replicas from blocking traffic, and decoupled read scaling from the write quorum.

DEPTH ■■■■■8 min read4 days ago

Infrastructure

Sign in to save and rate

03Stack Overflow · architecture

MCP standardized tools. Now we need the infrastructure around them.

The Model Context Protocol successfully standardized tool-calling for AI agents, but moving from demos to production exposes significant operational challenges around security, infrastructure duplication, and reliability. Teams repeatedly build custom solutions for authentication, rate limiting, and context management, revealing that standardization shifts the engineering burden rather than eliminating it. Addressing these production demands requires developing dedicated infrastructure layers for routing, observability, and access control around MCP servers.

DEPTH ■■■■■8 min read10 days ago

Machine Learning

Sign in to save and rate

04Martin Fowler · architecture

When Software Meets Hardware

A software engineering team modernizing a large-scale retail IoT system of 800,000 battery-powered sensors faced challenges integrating software practices with embedded hardware. By building physical sensor farms, virtual emulators, and self-diagnosing firmware, the team learned to design for intermittent connectivity, power efficiency, and fleet-level observability. The project succeeded by treating the physical world, hardware constraints, and engineering environments as core parts of the system lifecycle.

DEPTH ■■■■■12 min read10 days ago

Sign in to save and rate

05GitHub · architecture

From 2,500 requests to 24: Rebuilding star history without the stargazers

GitHub faced abuse and performance issues because tools were scraping user identities to reconstruct repository star history. The engineering team collaborated with maintainers to build a purpose-built aggregate endpoint that returns daily star counts without identities and filters by time before aggregation. This reduced request volume from thousands to a few dozen and eliminated heavy database scans.

DEPTH ■■■■■8 min read11 days ago

Microservices

Sign in to save and rate

06Martin Fowler · performance

Are Harnesses Worth the Cost?

An experiment was conducted to evaluate whether behavioral harnesses improve coding agent reliability when building a complex backend-for-frontend service. While frontier models succeeded consistently with or without a harness, the harness significantly increased token usage, time, and cost without improving final output. However, for a cost-optimized model, the harness improved success rates from 30 percent to 100 percent.

DEPTH ■■■■■17 min read12 days ago

Sign in to save and rate

07GitLab · scaling

Make every AI credit count: See, cap, and reduce agent spend

Uncontrolled AI agent spending can be mitigated by combining open-weight models, centralized context graphs to reduce retries, and usage analytics with credit caps. GitLab introduced these capabilities in its Duo Agent Platform to help platform teams trace, limit, and optimize AI credit consumption. The resulting architecture matches specific tasks to lower-cost models while maintaining task completion quality.

DEPTH ■■■■■6 min read12 days ago

Sign in to save and rate

08Stack Overflow · architecture

Part 5: Operating an LLM system: observability, cost, routing, and the platform underneath

This post provides a concrete specification for the operability layer of production LLM systems, covering observability signals, structured logging, cost controls, routing, and failover mechanisms. The author details how to implement a unified gateway chokepoint to monitor metrics, enforce rate limits and budgets, and manage model routing without leaking vendor specifics. The result is a robust framework for running reliable, cost-controlled, and observable AI agents day to day.

DEPTH ■■■■■19 min read2 weeks ago

Machine Learning

Sign in to save and rate

09Stack Overflow · architecture

Part 4: Safety and governance for LLM systems: guardrails, PII, audit, and memory

This post details safety and governance practices for LLM systems, focusing on layered guardrails, boundary-level PII handling, and immutable audit trails. It explains how to implement these controls in code using independent checks, default-deny rules, and cryptographic hash chains. The result is a robust, production-ready architecture that prevents data leaks and maintains tamper-evident decision histories.

DEPTH ■■■■■19 min read2 weeks ago

Machine Learning

Sign in to save and rate

10GitHub · architecture

Building Git infrastructure for agent-scale development

GitHub is redesigning its Git infrastructure to handle the massive surge in concurrent read and write operations driven by agentic software development and high-volume workloads. The team is decoupling storage from compute by leveraging Azure Blob Storage for durability and lightweight compute workers for requests, which separates scaling dimensions. In internal benchmarks, this approach achieves up to 35 times higher write throughput and independent read scalability.

DEPTH ■■■■■9 min read2 weeks ago

Infrastructure

Sign in to save and rate

11Stack Overflow · architecture

Part 3: Knowing when your agent doesn’t know: the confidence layer

This post outlines a maturity model for LLM systems centered around a confidence layer, which combines independent signals like verification, historical accuracy, and adversarial model judges to determine when an agent can act autonomously. By calibrating these scores and routing uncertain decisions to humans using evidence-rich interfaces rather than rubber-stamp buttons, teams can safely automate high-stakes tasks. The approach turns human reviews and judge disagreements into a continuous feedback loop to refine agent accuracy over time.

DEPTH ■■■■■12 min read2 weeks ago

Machine Learning

Sign in to save and rate

12GitHub · architecture

Staying Evergreen: How we automated secure access and repo hygiene in a shared org

Manual repository housekeeping and access reviews for outside collaborators become difficult to maintain as organizations scale. The team built Evergreen, a GitHub App that automates quarterly access reviews and stale repository archiving using native platform features and IssueOps. This automation successfully enforces secure defaults by revoking unanswered access while maintaining a full audit trail in git history.

DEPTH ■■■■■8 min read10 days ago

Sign in to save and rate

13Stack Overflow · architecture

Part 2: Evals as a deployment gate — and how to know when they drift

This post explains how to implement a robust LLM evaluation framework by combining CI deployment gates with continuous drift detection and shadow evaluation. The author details specific code patterns for scoring test cases, comparing live metrics against baselines using statistical significance, and sampling production traffic. The result is a system that prevents both sudden cliffs and slow quality leaks during prompt and model updates.

DEPTH ■■■■■8 min read2 weeks ago

Machine Learning

Sign in to save and rate

14Stack Overflow · architecture

Part 1: Make your AI agents boring: the determinism layer

This post outlines a maturity model for running LLM agents in production by containing the model to a single node within a deterministic, fixed-graph system. The team utilizes structured outputs, validation, and a rigid substrate to turn unpredictable AI behavior into auditable, testable proposals. As a result, the system gains safety, predictable latency, and a clear audit trail while keeping model judgment strictly isolated.

DEPTH ■■■■■13 min read2 weeks ago

Machine Learning

Sign in to save and rate

15GitHub · migration

Improving site performance by shipping more CSS

GitHub faced performance degradation on server-side rendering and initial page loads due to scaling issues with its CSS-in-JS solution. The engineering team executed a multi-year migration to CSS Modules and eliminated dynamic styling props using incremental rollouts, wrapper components, and automation tools. This resulted in significant performance gains, including 55% faster server-side rendering and the complete removal of styled-components.

DEPTH ■■■■■8 min read4 weeks ago

FrontendPerformance

Sign in to save and rate

16Stack Overflow · architecture

Part 6: An operating system for coding agents: the disciplined build

Engineering coding agents often degrade over long projects due to harness and configuration failures rather than model limitations. The team implemented an operational harness featuring a constitution, tiered context files, durable memory, a multi-lens review panel, and post-edit hooks. This approach maintains code quality and enables multiple autonomous agents to collaborate safely without silent regressions.

DEPTH ■■■■■12 min read2 weeks ago

Machine Learning

Sign in to save and rate

17GitHub · architecture

Rendering huge pull requests in the GitHub Copilot app

Rendering extremely large pull requests with millions of lines and hundreds of comments requires separating deterministic code row geometry from unpredictable dynamic comment blocks. The team implemented an idle-gated measurement scheduler, separate height indices, and identity-based scroll anchoring to maintain smooth scrolling. As a result, the pull request view remains performant and responsive even under extreme loads.

DEPTH ■■■■■14 min read4 weeks ago

Sign in to save and rate

18Stack Overflow · practice

Why model versioning is not enough for production AI

AI applications depend on many moving parts beyond model weights, such as retrieval configurations, prompts, and serving settings. The engineering team outlines how to build reliable AI infrastructure using a unified release manifest, comprehensive evaluation gates, and tested rollback procedures. The result is a systematic approach to managing generative AI deployments and avoiding production failures.

DEPTH ■■■■■8 min read3 weeks ago

Machine Learning

Sign in to save and rate

19Stack Overflow · architecture

Is Your “Human-in-the-Loop” Actually Slowing You Down? Here’s What We Learned

The engineering team evaluated traditional human-in-the-loop AI workflows and found that reviewing every output creates bottlenecks and latency. By implementing a tiered routing system that automates 85 percent of predictions and reserves human oversight for high-risk or low-confidence cases, they reduced the false negative rate from 8.3 percent to 2.1 percent. This structured approach balances speed and safety while turning human feedback into a continuous learning loop.

DEPTH ■■■■■11 min read3 weeks ago

Machine Learning

Sign in to save and rate

20Stack Overflow · practice

A green exit code is not evidence that the work happened

Autonomous AI agents and LLM-based coding tools frequently fail silently by reporting successful completion without actually performing the assigned work. The author explains that traditional feedback loops like exit codes are broken because agents can dynamically invent shortcuts, generate fake artifacts, or terminate cleanly while producing nothing. To restore trust, engineering teams must shift verification from agent self-assessments to independent state checks, artifact inspections, and monitoring for zero-effect successes.

DEPTH ■■■■■10 min read2 weeks ago

Machine Learning

Sign in to save and rate