/ THE FEED /

Read what ships.

Deep, recent reads ranked by depth and freshness.

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

  2. The Shift to cgroup v2 in Kubernetes: What You Need to Know

    Kubernetes has deprecated cgroup v1 in favor of cgroup v2, with complete removal scheduled for future releases. The transition requires migrating Linux nodes, updating container runtimes, and verifying kernel compatibility. Adopting cgroup v2 enables advanced features such as Memory QoS, improved OOM handling, and pressure stall information metrics.

    DEPTH ■■■■■12 min read2 weeks ago

    Sign in to save and rate

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

  4. Scaling Kubernetes Workloads with Node Swap

    Kubernetes memory limits often cap node density for bursty agentic AI workloads that sit idle with large memory footprints. To solve this, the engineering team benchmarked Kubernetes v1.34 node swap backed by fast NVMe Local SSDs across CI/CD builds, headless browsers, and Python sandboxes. The approach successfully increased pod density up to three times without significant latency costs.

    DEPTH ■■■■■6 min read2 weeks ago

    Sign in to save and rate

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

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

  7. It's time to make your own RSS reader

    This post walks through the process of self-hosting a personal RSS reader using FreshRSS and Docker, secured privately over a Tailscale network. The author details the configuration of environment variables, auth keys, and Docker compose deployment to avoid exposing the service to the open web. The result is a private, algorithm-free news reader accessible across multiple devices and integrable with external reading apps or AI agents.

    DEPTH ■■■■■10 min read9 days ago

    Sign in to save and rate

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

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

  10. Why Is My Kubernetes Job Still Pending? Tracing Kueue Admission with Headlamp

    Kubernetes jobs managed by Kueue can remain pending while waiting for admission checks and resource allocation. The team implemented a Kueue plugin for Headlamp to trace pending workloads through local queues, cluster queues, and resource flavors within a unified interface. This approach allows engineers to quickly determine whether a job is blocked by admission policies or standard pod scheduling.

    DEPTH ■■■■■9 min read11 days ago

    Sign in to save and rate

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

  12. Your agent, your network: How Meta’s Muse agent works with Tailscale

    Meta integrated Tailscale into its Muse personal AI agent, allowing the agent to join a user's tailnet as a separate node and interact with self-hosted services and SSH sessions. By treating Muse like any standard tailnet node, users can apply Tailscale's access controls, grants, and tags to enforce security and adhere to the principle of least privilege.

    DEPTH ■■■■■5 min read3 weeks ago

    Sign in to save and rate

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

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

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

  16. “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

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

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

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

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