/ THE FEED /

Read what ships.

Deep, recent reads ranked by depth and freshness.

  1. A Deep Dive into Salesforce’s Agent Tech Stack

    Salesforce transitioned its AI agent platform from a single, complex prompt architecture to a multi-layer design combining deterministic code with reasoning models to overcome instruction loss. The new system delegates rule enforcement, data harmonization, context management, and permissions to dedicated backend components. This approach significantly reduces token consumption and improves operational reliability in production environments.

    DEPTH ■■■■■13 min readyesterday

    Sign in to save and rate

  2. We gave AI agents a mobile dev environment

    Engineering teams outgrew their local machines while running parallel AI mobile development agents, constrained by heavy builds and lack of iOS tools on Linux. To solve this, they built Remote Dev using warm pools of remote Macs connected via SSH alongside separate Linux VMs for Android virtualization, paired with agent skills and live browser streaming. This setup shifted workflow bottlenecks, increasing AI-merged pull requests from 6 percent to 61 percent.

    DEPTH ■■■■■9 min read5 days ago

    ArchitectureMobile

    Sign in to save and rate

  3. 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 read6 days ago

    Infrastructure

    Sign in to save and rate

  4. App stability at scale with a layered defense

    To maintain app stability amidst rapid weekly releases and AI-generated code, Grab uses a layered defense strategy covering prevention, release gates, and incident response. This pipeline includes static analysis via custom lint rules, multiple tiers of automated and manual testing, a pre-production early access build, staged rollouts, and feature flags with instant kill switches. As a result, critical defects are caught early in the development lifecycle before reaching the wider production user base.

    DEPTH ■■■■■16 min read6 days ago

    MobileReliability

    Sign in to save and rate

  5. How Shopify turns open models into task experts

    Shopify uses a continual learning flywheel to post-train open models, such as NVIDIA Nemotron, to serve as dedicated subagents for specific tasks like GraphQL generation. By optimizing inference and utilizing automated self-healing to generate training data from production failures, the team successfully created task experts that outperform frontier models while reducing serving costs by 90-98% and improving response times.

    DEPTH ■■■■■5 min read6 days ago

    Architecture

    Sign in to save and rate

  6. Why Shopify Migrated From React Native

    Shopify migrated its mobile applications from React Native to native Swift and Kotlin because AI coding agents made the cost of duplicating features across platforms negligible. Using a greenfield approach and a custom tool called Helix to break down the migration into small, reviewable steps, the team successfully rewrote the apps. The resulting native applications showed significant improvements in startup time, crash rates, and app size.

    DEPTH ■■■■■11 min read7 days ago

    Sign in to save and rate

  7. 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 read12 days ago

    Microservices

    Sign in to save and rate

  8. Cross-store product clustering across millions of stores

    Shopify needed to group identical product listings from millions of different merchants under a single global identifier. To solve this at scale without comparing every possible pair, the team implemented a multi-stage pipeline using vector retrieval, a tiered scoring system of ML models, and a bounded graph clustering approach. This architecture successfully standardizes product data across the entire platform while controlling computational costs.

    DEPTH ■■■■■13 min read7 days ago

    Architecture

    Sign in to save and rate

  9. How Uber Built a Genie to Answer Questions Correctly

    Uber built an internal AI assistant called Genie to answer engineering support questions directly within Slack. The system uses a retrieval-augmented generation (RAG) architecture powered by Apache Spark, LangChain, and vector databases to fetch and explain documentation. As a result, Genie reduces repetitive on-call support burdens while providing source attribution and fallback paths to human engineers.

    DEPTH ■■■■■13 min read8 days ago

    Sign in to save and rate

  10. Building Overexposed: understanding application exposure

    The team built an automated scanner called Overexposed to track internet-facing services and verify access controls across Kubernetes and Cloud Run. By querying live cloud inventories and probing endpoints like an outsider, the scanner classifies exposure while avoiding false assumptions from static config files. As a result, the engineering organization improved accuracy and significantly reduced inconclusive findings over time.

    DEPTH ■■■■■8 min read7 days ago

    Sign in to save and rate

  11. Powering AI-led research through simulation

    The engineering team built a self-contained simulation platform called sim-rs to model marketplace dispatch dynamics and accelerate experimentation. By connecting automated software agents to this simulator with strict safety safeguards, the team successfully optimized strategy policies and simulator performance. This closed-loop lab environment allows agents to test ideas rapidly while ensuring that only valid, production-ready improvements are produced.

    DEPTH ■■■■■10 min read3 weeks ago

    Machine Learning

    Sign in to save and rate

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

  13. LLM Prompt Caching Versus Semantic Caching

    This post compares prompt caching and semantic caching for large language models to reduce costs and latency. Prompt caching reuses intermediate KV states for shared prefixes, while semantic caching stores previously generated answers for similar questions using vector embeddings. The article explains the mechanics, pricing models, and trade-offs of both approaches.

    DEPTH ■■■■■16 min read6 days ago

    Sign in to save and rate

  14. Front-End Web Deep Dive: Runtime Config

    Front-end web applications traditionally bake environment variables into build artifacts, requiring a full rebuild to change configurations across environments. To solve this, a new approach injects runtime environment variables directly into the HTML document's head element as data attributes via a Cloud Native Buildpack. This enables zero-rebuild configuration changes while remaining compatible with browser security standards like CSP.

    DEPTH ■■■■■3 min read12 days ago

    Frontend

    Sign in to save and rate

  15. 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 read11 days ago

    Sign in to save and rate

  16. How Netflix Taught an LLM to Recommend Movies So That You Keep Watching

    Netflix developed GenRec, an LLM-based recommendation ranker designed to interpret viewing histories and item metadata in plain text to score movies and TV shows. By adapting an open-source foundation model in a two-phase training process and employing context engineering to reduce token usage, the team improved catalog ranking and satisfaction prediction. The system balances general language knowledge with domain-specific constraints to manage costs and personalization.

    DEPTH ■■■■■15 min read2 weeks ago

    Sign in to save and rate

  17. ShopGym: Realistic, reproducible sandboxes for shopping agents

    Training and evaluating shopping agents is difficult due to changing live store environments, bot detection, and limited hand-built test stores. The team developed ShopGym, a framework that converts live storefronts into self-contained, anonymized sandbox shops and generates benchmark tasks. Evaluation showed that synthetic shops preserve key structural properties and behavioral alignment with live stores, giving agents a reliable environment to practice and improve.

    DEPTH ■■■■■6 min read3 weeks ago

    Sign in to save and rate

  18. Why LLMs Agree With You Even When You’re Wrong

    Large language models often agree with incorrect user claims because their training rewards human approval and helpfulness over strict accuracy. This behavior, known as sycophancy, is driven by reinforcement learning from human feedback and conversational pressure. Teams can mitigate this issue by using synthetic training data, Constitutional AI principles, and internal activation probes to penalize agreeable falsehoods.

    DEPTH ■■■■■13 min read3 weeks ago

    Sign in to save and rate

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

  20. The LLM Blindspot: Why Models Forget What’s in the Middle of Your Prompt

    Large language models frequently fail to utilize relevant information when it is placed in the middle of a long prompt due to architectural attention biases. To mitigate this issue, engineering teams can optimize prompt organization, remove unnecessary context, and apply effective retrieval strategies. Ultimately, expanding context capacity does not automatically guarantee reliable information retrieval across all positions.

    DEPTH ■■■■■11 min read3 weeks ago

    Sign in to save and rate