Loading…
Latest reads
Every post, summarised
Grounded summaries of engineering blogs, newest first. Each links to the original.
- 4,671 posts
- 20 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Latest posts
Beyond code generation: rethinking engineering productivity in the age of AI agents
Dropbox shares how widespread AI code generation shifts software development bottlenecks downstream into code review, CI infrastructure, and validation pipelines. To adapt, they built Nova, an internal coding agent platform that safely automates scoped tasks such as migrations and flaky test remediation. They also evolved their developer productivity framework to measure end-to-end customer impact and code quality rather than simple pull request throughput.
Slack AI: The Path to Multi-Cloud
Slack evolved its Slack AI serving infrastructure across multiple phases to handle enterprise LLM workloads reliably and securely. The initial deployment on AWS SageMaker provided zero-knowledge escrow VPC isolation and FedRAMP compliance, but engineers faced scaling latency, GPU scarcity, and significant operational overhead. Slack then migrated live traffic to Amazon Bedrock to leverage managed Model Units and eliminate model release lag without customer-facing incidents. However, fixed Provisioned Throughput commitments and regional peak traffic variations created persistent underutilization challenges. Consequently, Slack expanded into a multi-cloud orchestration architecture that normalizes disparate provider APIs, integrates unified cross-cloud telemetry, and routes traffic dynamically around latency spikes and outages.
Modernizing Artifact Storage at Uber
Uber’s legacy artifact platform used two five-node clusters with local disks, asynchronous replication, and GeoDNS failover to support builds across monorepos and microrepos. As artifact volume grew, limited node capacity, inconsistent replication, manual hardware evacuation, and risky multi-terabyte upgrades created operational and data-loss risks. Uber moved to a managed SaaS platform with multi-region availability, cross-region replication, and cloud-native blob storage, then added an internal validation proxy in front of it. The proxy uses MySQL metadata and conditional requests, including If-None-Match and If-Modified-Since, to validate artifacts against the SaaS origin while reusing unchanged bytes; failures can fall back to passthrough, preserving correctness at higher latency and egress cost. The design reduced operational risk, improved observability, and made artifact delivery more cost-efficient at scale.
Anthropic opens Milan office to support Italian enterprise, research, and developers
Anthropic will open a Milan office, its sixth in Europe, to work with Italian companies and developers building and scaling with Claude responsibly and to join Italy’s broader conversation about AI. Led by Thomas Remy, Head of Southern Europe, the team already works with companies including Generali Group, Unipol Group, Angelini Pharma, Bracco Group, Enel Group, and Pirelli. A partnership with JAKALA has deployed Claude across more than 3,000 seats to free up roughly 70% of senior team time for higher-judgment client work, while Satispay compressed an 18-month roadmap into seven months. The office follows the presentation of Magnifica Humanitas, where Chris Olah addressed AI ethics, and will also support research, culture, and design through initiatives such as an Alcova Milano workshop.
amazon.science
How flat is replacing fat in AWS data center networks
Traditional data center networks rely on hierarchical fat-tree topologies, which introduce overhead, upper-layer congestion, and vulnerability to router failures. Although flat random networks theoretically maximize route diversity and resilience, routing computation and cabling complexity historically made them impractical for physical data centers. AWS addressed these constraints by introducing Resilient Network Graphs, a quasi-random architecture powered by a passive optical device called ShuffleBox and a routing algorithm named Spraypoint. Spraypoint sprays packets across random neighbors toward designated waypoints, unlocking twice as many independent paths while operating within commodity router memory limits. Adopted as the default architecture across new AWS facilities, this design reduces router counts by 69%, lowers projected network power consumption by 40%, and increases throughput by up to 33%.
How we cut build times by two-thirds by deleting our CMS
Sentry rebuilt its marketing site and blog of roughly 2,500 pages, replacing a legacy Gatsby setup and traditional headless CMS with Astro, Markdown, Frontmatter, and AI-driven automation. The previous architecture suffered from 14-minute build times, restrictive CMS schema limits, and frequent build failures caused by external API dependencies. A team of 2.5 developers executed the migration in two months using Claude Code agents for data extraction, template translation, and testing. To manage content without a CMS dashboard, Sentry built Claude Skills to guide updates, run local previews, and draft GitHub pull requests. The migration reduced average build times to under 4 minutes, cut broken staging builds by 95 percent, and improved Web Vitals scores from 89 to 97.
6 Tips for Accessible Emails
The Email Markup Consortium’s 2026 report analyzed 376,348 emails and found that only eight passed every accessibility check, while nearly all failures included Serious or Critical issues. The post focuses on six largely mechanical improvements: setting lang and dir, marking layout tables role=“presentation”, creating a heading hierarchy, writing descriptive link and image text, adding a specific title element, and meeting a 4.5:1 color-contrast ratio. It gives HTML examples, notes that clients may strip attributes from the html element, and distinguishes meaningful images from decorative ones that need empty alt text. It also describes updated React Email defaults for language, direction, image alt text, Markdown tables, and titles, while leaving content judgments such as headings, links, and contrast to authors.
Supercharge your integration workflow with the Google Pay & Wallet Developer MCP server
Google Pay & Wallet Developer MCP server is announced to help AI assistants and IDEs complete Google Pay and Google Wallet API integrations with less context switching. It uses Model Context Protocol to connect tools including Antigravity, Cursor, and Visual Studio Code with current documentation, account details, and integration status. Its search_documentation tool applies Retrieval-Augmented Generation to return answers and code samples from official developer sites, while other tools validate Wallet pass JWTs or JSON, expose performance metrics and error trends, and manage merchant accounts and Google Pay API integrations. The stated goal is to reduce friction, improve accuracy with current documentation and real account data, and speed troubleshooting from setup through launch. A public guide and tool reference are available, with further capabilities planned based on developer feedback.
Under the River
Shopify describes how its AI agent, River, grew from an infrastructure bet aimed at making a large, fragmented codebase usable by AI. In early 2024, the company adopted a monorepo called World and Nix as a reproducible substrate for development, CI, and production, despite substantial migration costs. River operates in public Slack channels, where it reads code, runs tests, queries data, inspects production traces, and opens pull requests; in a recent 30-day period it handled 59,918 sessions and contributed to 3,536 merged pull requests. Underneath it, Aquifer provides durable sessions, sandboxes, gateways, event logs, credentials handling, and observability, allowing agent profiles to share one platform across interactive, automated, and batch modes. The central design principle is that the session must survive process and machine failure, while public transcripts create a compounding knowledge corpus.
Open House 2026 Day 2: 10 years of open source and what the ecosystem is building next
Open House 2026 Day 2 recaps ClickHouse’s tenth year as an open-source project and the ecosystem forming around its data platform. The event reported more than 2,600 contributors, nearly 48,000 GitHub stars, over 200 integrations, and the launch of the House Mates partner program. Announcements included Fivetran’s generally available ClickHouse Cloud destination, a Google Cloud Dataflow Pub/Sub template, Sigma’s public-beta connector and ETL Cache Layer, and a ClickHouse dbt Fusion adapter available in alpha through the CLI. The recap also describes MCP and agent-oriented observability work, including a ClickStack MCP server that translates investigations into optimized ClickHouse queries. Internal testing reported up to 25% fewer tool calls, 2.5 times greater consistency, and nearly 20% better evaluation results.
Open House observability announcements: MCP server, AI Notebooks, and ClickStack Cloud
At Open House, ClickHouse announced three observability updates: ClickStack Cloud entered private preview, AI Notebooks entered beta for Managed ClickStack, and a ClickStack MCP server was introduced in open-source ClickStack. ClickStack Cloud is a fully managed, serverless platform that accepts OpenTelemetry data through a managed endpoint, while Managed ClickStack is generally available for teams controlling collectors, ingestion, compute sizing, schema design, and tuning. AI Notebooks provide a persistent, shareable investigation workspace in which prompts, queries, charts, reasoning steps, findings, branches, intermediate results, and generated queries remain visible and editable. The MCP server exposes the investigative tools used by Notebooks to external agents, routing requests through optimized searches, aggregations, and visualizations rather than relying entirely on ad hoc SQL generation; it can also persist findings in dashboards. Together, the announcements present a choice between managed convenience, operational control, and programmable observability workflows.
Reliable LLM Inference at Scale
Databricks describes an inference platform serving open-source and proprietary frontier models at more than 125T tokens per month, with reliability as the central challenge under spiky, multi-tenant demand. It identifies failures and latency risks from expensive GPU configurations, variable input and output lengths, long-context requests, multimodal preprocessing, and engine-level hangs. Its architecture combines rate limiting, capacity management, model units, Dicer load-aware sticky routing, and autoscaling; model units estimate multidimensional request cost and allocate capacity more predictably. For runtime reliability, prioritized black-box health checks trigger Kubernetes liveness restarts for silent hangs, completing detection and recovery in less than five minutes while eliminating false probe failures. Image-processing changes, including Torchvision processors and OMP_NUM_THREADS configuration, removed CPU throttling and increased completed requests per second by more than threefold with the same replicas and load; bursty workloads also achieved over 80% GPU savings versus static peak provisioning.
BI Serving Pointers; Maximizing for Performance and TCO
BI dashboards can become slow and expensive when teams respond to latency with separate aggregate tables, refresh pipelines, extracts, and tool-specific semantic layers. The post presents Databricks’ BI serving stack from physical storage through Unity Catalog’s governed semantic layer, recommending Gold-layer star schemas, managed tables, liquid clustering, and Predictive Optimization to reduce scanned data and improve query plans. Metric Views centralize KPI definitions and semantic metadata for dashboards, Genie, SQL notebooks, third-party BI tools, and AI agents, while materialization automatically maintains incremental pre-aggregations and routes queries transparently. Additional TCO guidance covers serverless SQL warehouse autoscaling, DBSQL disk and query-result caching, direct lakehouse connections, and system-table monitoring. The stated outcome is compounded lower latency and compute cost, including an observed average 22% performance improvement from Predictive Optimization and sub-second performance from materialized metrics.
Thank you for building with us
At its 2026 user conference in San Francisco, ClickHouse reports surpassing 4,000 customers and $250 million in annual run-rate revenue, while marking nearly ten years since Alexey Milovidov open-sourced the database. The company attributes its growth to a community of contributors and describes use across AI products, financial services, observability, analytics, and infrastructure. New offerings include ClickHouse Agents, a fully managed agentic analytics service powered by Anthropic’s Claude; CostBench, an open benchmark using each warehouse’s real billing model; and House Mates, a partner program launching with more than 50 partners across six continents. Additional updates include Managed Postgres in public beta, Managed ClickStack and Langfuse for AI-era observability, generally available full-text search, and automatic JOIN optimization, with cost-performance identified as the central constraint for high-concurrency, low-latency workloads.
ClickHouse tops $250M ARR and 4,000 customers, launches Claude-powered agents at Open House 2026
At Open House 2026, ClickHouse announced that its serverless cloud offering exceeded $250 million in annual run-rate revenue and reached 4,000 customers, with ARR more than tripling year-over-year and more than 1,000 net new customers added since January. The company launched ClickHouse Agents, a fully managed, no-code agentic analytics service powered by Anthropic’s Claude, with a chat interface, sandboxed code interpreter, artifacts, skills, memory, multi-agent workflows, and MCP-compatible integrations. It also published CostBench, an open benchmark applying each vendor’s real compute billing model to the same workload; ClickHouse Cloud was reported to have 23x better cost-performance than the nearest cloud data warehouse. Other announcements included Managed Postgres in public beta, managed ClickStack, generally available full-text search, cross-region replication, and the House Mates partner program.
amazon.science
Amazon Research Awards recipients announced
Amazon Research Awards has announced 70 award recipients across 49 universities in 11 countries for its fall 2025 funding cycle. The funded research spans six distinct tracks: AI for Information Security, Agentic AI, Automated Reasoning, AWS Cryptography, Cybersecurity and Anti-Abuse Technologies, and Sustainability. Each selected academic team receives unrestricted financial grants, AWS Promotional Credits to access specialized cloud AI and machine learning services, and access to more than 700 Amazon public datasets. Awardees are paired with an Amazon research contact who provides advisory support, consultation, and access to company training sessions. Furthermore, the program explicitly encourages recipients to publish their discoveries, deliver presentations at Amazon offices worldwide, and release associated software implementations under open-source licenses.
The ultimate guide to knowledge management for your Service Agent
AI-driven customer service depends on knowledge management because a Service Agent needs accurate product, feature, policy, and troubleshooting information to resolve queries end to end. The guide divides the work into two phases: building a knowledge base, and maintaining, optimizing, and scaling existing content. It recommends using support conversations and tools such as Fin Recommendations to identify gaps, prioritize FAQs, onboarding guides, troubleshooting material, and other resources, then centralize content and control what the Agent can use. Ongoing practices include scheduled reviews, a request log, launch-planning updates, consistent terminology, audience targeting, and contact details for escalation. The stated conclusion is that knowledge management should be a continuous core service function, with improvements producing more resolutions, better data, and further opportunities to refine support.
Introducing Always-On pricing: automatic savings for Databricks Lakebase
Databricks introduces Always-On pricing for Lakebase, offering a lower rate for baseline compute while retaining elastic autoscaling. On any Lakebase Postgres Autoscaling project, operators turn off scale-to-zero and set an autoscaling range; the minimum capacity becomes the baseline, which receives the lower rate after 24 hours of continuous use. Capacity above the minimum continues to autoscale up to the configured maximum and is billed at standard Autoscaling rates, while users can re-enable scale-to-zero later. The pricing targets established workloads with a consistent activity floor; intermittent or new workloads can retain scale-to-zero to avoid paying for idle hours and uncertain baseline estimates. The announcement says the baseline price is 25% lower, and an additional 50% promotional discount runs through January 31, 2027.
How the lakebase architecture stays resilient to cloud failures
Lakebase is adapting its reliability architecture to agentic and on-demand workloads, which create far more control-plane activity, database starts, and pressure on finite cloud capacity. Lakebase uses stateless Postgres compute over zone-resilient storage, dedicated multi-availability-zone computes for optional high availability, and a vertically autoscaling virtualization layer that reduces dependence on cloud provisioning control planes. A dedicated data-plane controller is being developed for hot-path start and suspend operations, while cell-based regional deployments isolate failures and allow capacity to expand incrementally. The reliability program also uses component and whole-availability-zone failure injection, consistency checks, Service Level Indicators, and Service Level Objectives, including startup, failover, storage, and API measurements. The stated target is for every database to exceed 99.99% monthly availability; reported 2026 attainment through April shows 99.75% to 99.85% of databases meeting that threshold.
Announcing Lakebase Change Data Feed (CDF)
Lakebase Change Data Feed (CDF) is available in Public Preview to reduce the manual effort of moving data from operational databases into downstream systems. The feed is enabled once for all tables in a project, stored and governed in Unity Catalog Managed Tables, and readable by engines, models, and agents without separate extraction pipelines. From one shared feed, teams can build streaming pipelines with SDP, create materialized views with DBSQL, or compute and store embeddings with Agent Bricks, while consumers remain isolated from the primary operational workload. The announcement positions Lakebase as the native Bronze layer in a medallion architecture, complementing Synced Tables and providing governance and lineage across the data lifecycle.
Top topics
- Architecture834
- Performance816
- LLMs660
- Machine Learning622
- Open Source563
- AI Agents553
- AI470
- Developer Experience448
Weekly digest
The best engineering reads, once a week.