/ THE FEED /

Read what ships.

Deep, recent reads ranked by depth and freshness.

  1. How Etsy gets its mobile apps ready for peak traffic

    Etsy prepares its mobile apps for peak holiday traffic through advance planning, operational guardrails, and risk management rather than relying on capacity scaling or the ability to quickly revert binaries. The engineering team utilizes a phased code slush, dual crash reporting, remote feature flags, and custom error tagging to surface and mitigate issues effectively under heavy loads. By connecting crash rates to business metrics and automating manual triage workflows incrementally, the organization maintains high visibility and reliability when updates cannot be instantly rolled back.

    DEPTH ■■■■■11 min read3 weeks ago

    Sign in to save and rate

  2. 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

  3. Architect highly available Oracle Database on Amazon EVS and FSx for ONTAP

    Enterprises migrating Oracle databases to Amazon Elastic VMware Service face challenges with storage latency, disaster recovery, and operational consistency. The team designed a highly available architecture combining Amazon EVS bare metal instances with Amazon FSx for NetApp ONTAP NFS datastores and cross-region SnapMirror replication. The resulting setup delivers sub-millisecond storage latency, preserved VMware operational workflows, and robust disaster recovery capabilities.

    DEPTH ■■■■■12 min read3 weeks ago

    Sign in to save and rate

  4. 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

  5. Deploy open source Regional availability tools in your VPC

    Engineering teams planning multi-Region architectures often struggle with evaluating AWS service availability and managing compliance risks. The team built and open-sourced two VPC-hosted solutions that deploy an automated Regional availability dashboard and a workload analysis pipeline using CloudTrail and CloudFormation. This setup allows organizations to securely filter and inspect the 20 to 30 services they actually use instead of hundreds.

    DEPTH ■■■■■13 min read3 weeks ago

    Sign in to save and rate

  6. 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

  7. Accelerating airline retailing innovation: how Datalex modernized with AWS Experience-Based Acceleration and agentic AI

    Datalex partnered with AWS for a three-day Experience-Based Acceleration workshop to modernize its mission-critical airline retail platform from Java 8 and EJB2 to Spring Boot on Java 21. The team used parallel workstreams and agentic AI to prove migration feasibility, implement automated CI/CD pipelines, and integrate generative AI capabilities without disrupting existing airline operations. This effort successfully established repeatable migration patterns, reduced memory usage by 35%, and accelerated the timeline for long-term platform evolution.

    DEPTH ■■■■■14 min read3 weeks ago

    Sign in to save and rate

  8. Application Metrics caught my broken size estimator

    An engineer integrated application metrics into a client-side video conversion tool to monitor file size estimation accuracy without using invasive telemetry. By tracking key performance indicators and analyzing the metric distributions, they discovered that an AI-generated estimation formula was flawed and producing results off by up to 83 percent. Replacing the broken logic with a correct bitrate-based formula brought the size estimation accuracy to within five percent of real-world results.

    DEPTH ■■■■■15 min read7 weeks ago

    Sign in to save and rate

  9. Running multi-day AZ evacuation drills with ARC Zonal Shift

    This post explains how to run multi-day Availability Zone evacuation drills using ARC Zonal Shift to prove application resilience under sustained stress. The team details step-by-step procedures across ECS, EKS, and PostgreSQL databases to uncover hidden failure modes like unoptimized scaling and stale connections. The result is a practical framework for moving from theoretical multi-AZ architectures to proven operational resilience.

    DEPTH ■■■■■19 min read3 weeks ago

    Sign in to save and rate

  10. “Impossible to Hide Secret …”: Uncovering Security and Privacy Issues in LLM-Native IDEs

    Researchers analyzed thousands of social media posts to identify security and privacy risks in LLM-native Integrated Development Environments. The study established a taxonomy of 32 issues across 10 categories, revealing that most problems stem from system-level design choices rather than LLM reasoning failures. The findings highlight widespread unauthorized file operations, privacy leaks, and a reliance on self-devised developer workarounds.

    DEPTH ■■■■■3 min read2 weeks ago

    Machine LearningSecurity

    Sign in to save and rate

  11. Seer, the Sentry MCP and CLI, or your own coding agent: where each one fits

    Engineers often struggle to choose between native debugging agents, Model Context Protocols, and command-line tools when integrating error tracking into their workflows. Sentry demonstrates how its debugging assistant Seer, the Sentry MCP, the Sentry CLI, and various coding agent integrations complement each other rather than compete. The resulting setup allows teams to diagnose complex application errors and automatically generate pull requests through whichever surface they prefer.

    DEPTH ■■■■■11 min read3 weeks ago

    Sign in to save and rate

  12. How MHK built a HIPAA-eligible agentic AI solution on Amazon Bedrock

    Healthcare technology company MHK faced fragmented AI infrastructure and lengthy development cycles while trying to process unstructured medical documents under strict HIPAA standards. To solve this, they built a multi-tenant, event-driven agentic workflow framework called the SmartProminence AI Orchestrator on AWS using Amazon Bedrock, ECS, and SQS. The new system reduced manual review effort by 90% and shortened AI feature deployment times from months to weeks.

    DEPTH ■■■■■12 min read3 weeks ago

    Sign in to save and rate

  13. The Regression Tests Nobody Writes: Capturing How Software Actually Behaves

    Standard regression tests usually only verify developer intent rather than the actual, unwritten behaviors that systems accumulate in production over time. By capturing real production traffic and network-level interactions, teams can build characterization test suites to automatically detect unintended behavioral shifts. This approach prevents accidental regressions during legacy refactoring, rewrites, and major framework upgrades.

    DEPTH ■■■■■6 min read3 days ago

    Testing

    Sign in to save and rate

  14. Build adaptive AI interfaces with the AG-UI protocol, agent swarms, and Nova Act on AWS

    AI applications produce variable outputs that cannot be effectively handled by static user interfaces, leading to development friction and poor user experiences. The team implemented an adaptive interface pattern using the AG-UI protocol, the Strands Agents SDK Swarm pattern, and Amazon Nova Act on AWS to dynamically render components and automate legacy integrations. This architecture streams agent findings over Server-Sent Events, enabling real-time multi-agent consensus and reducing interface development overhead.

    DEPTH ■■■■■22 min read3 weeks ago

    Sign in to save and rate

  15. Survey Says: You'll swap the model, but everything you build around it is staying put

    Stacklok surveyed technical leaders to understand enterprise AI adoption and vendor lock-in concerns. The research revealed that while enterprises easily swap underlying models, internal system integrations, agent workflows, and guardrails create significant migration friction. Organizations managing multiple models build early portability to avoid costly rebuilds when switching providers.

    DEPTH ■■■■■4 min read4 days ago

    Machine Learning

    Sign in to save and rate

  16. Measuring the back/forward cache with Application Metrics

    Engineering teams often lack visibility into back/forward cache performance because successful cache hits leave no telemetry traces and browser heuristics frequently change. To solve this blind spot, the team introduced an opt-in application metrics integration in their JavaScript SDK that models browser bfcache signals into hits, specific miss reasons, and reload durations. As a result, developers can track, query, and fix silent navigation regressions using customizable dashboards.

    DEPTH ■■■■■6 min read4 weeks ago

    Sign in to save and rate

  17. Don't forget about the UI for AI

    OpenAI developed ChatGPT Space, a real-time collaborative workspace designed to allow software engineering teams and individual AI agents to work together on shared artifacts. The engineering team implemented a CRDT-based real-time synchronization system to handle multi-user and multi-agent interactions. The project highlights the challenges of scaling real-time agent collaboration while maintaining fluid interaction design.

    DEPTH ■■■■■26 min read5 days ago

    Machine Learning

    Sign in to save and rate

  18. Building Sentry's Laravel AI Integration

    The Sentry team built a Laravel AI integration to support Agent Tracing during an internal hackweek. Because Laravel AI lacked events for individual LLM invocations, the integration correlates outgoing HTTP requests with active invocations using provider URL prefixes. The resulting zero-config feature is available in sentry-laravel 4.27 and automatically traces agents, LLM requests, and tool calls.

    DEPTH ■■■■■4 min read4 weeks ago

    Sign in to save and rate

  19. Production-grade LLMs and agents: a field guide

    Deploying LLMs and agents to production requires surrounding probabilistic models with deterministic machinery like evaluations, guardrails, and audit trails rather than relying on the model alone. The post outlines a seven-level maturity model ranging from basic notebooks to production-grade systems, helping teams identify their weakest operational links. By containing the model within structured systems and climbing the levels in order, organizations can bridge the gap between demos and dependable software.

    DEPTH ■■■■■4 min read6 days ago

    Machine Learning

    Sign in to save and rate

  20. How Dynata scaled AI across the development lifecycle with AI-DLC and Kiro IDE

    Dynata adopted the AI-Driven Development Lifecycle methodology using Kiro IDE and Amazon Q Developer to compress multi-sprint feature delivery into a single sprint. The team progressed from code generation to integrating knowledge ecosystems and conducting structured three-day feature workshops. As a result, requirements ambiguities surfaced early during planning and the team achieved faster, more aligned feature delivery.

    DEPTH ■■■■■15 min read10 days ago

    Sign in to save and rate