---
title: "Latest reads"
description: "The engineering internet, summarised so you can actually read it."
---

# Latest reads
> The engineering internet, summarised so you can actually read it.

## Articles

### [The Data Canary: How Netflix Validates Catalog Metadata](https://yomu.fyi/post/the-data-canary-how-netflix-validates-catalog-metadata.md)
- Company: [Netflix](https://yomu.fyi/company/netflix.md)
- Author: Netflix Technology Blog
- Published: Jun 19, 2026
- Type: Problem & solution

A manual mitigation action during an incident corrupted a data feed for a subset of titles, causing playback issues and catalog service failures that existing code canary systems failed to catch. To protect streaming reliability, Netflix built an automated data canary system that validates transformed catalog metadata prior to publication. The architecture utilizes a dedicated orchestrator alongside permanent baseline and canary service clusters to coordinate validation using real production traffic. By leveraging custom chaos experiment thresholds, sticky session affinity, and Starts Per Second playback metrics, the system detects regressions in under ten minutes and blocks publication automatically. Controlled failure injection experiments routing approximately 0.2% of global traffic confirmed that issues could be identified in 2.5 to 4 minutes.


### [Dispatches from O'Reilly: From capabilities to responsibilities](https://yomu.fyi/post/dispatches-from-o-reilly-from-capabilities-to-responsibilities.md)
- Company: [Stack Overflow](https://yomu.fyi/company/stack-overflow.md)
- Author: Artur Huk
- Published: Jun 19, 2026
- Type: Problem & solution

High-stakes AI agents capable of mutating external state often face governance failures when relying on system prompts or manual Human-in-the-Loop approval queues that quickly degrade into alert fatigue. The Responsibility-Oriented Agent architecture addresses this operational bottleneck by shifting system design from open-ended capability framing to deterministic, contract-enforced responsibilities. Under this model, underlying orchestration frameworks like LangChain operate in User Space with their side-effecting tools removed, isolating the agent to epistemic reasoning. The agent expresses its intended action exclusively by emitting a structured policy proposal to a privileged Kernel Space runtime. The runtime deterministically evaluates the proposal against versioned YAML contracts registered in an agent registry, ensuring that only genuine policy exceptions are escalated to human supervisors.


### [Ten years of open source: a stained-glass view](https://yomu.fyi/post/ten-years-of-open-source-a-stained-glass-view.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Jun 19, 2026
- Type: Explainer

ClickHouse’s ten-year open-source history is presented through a stained-glass analogy: many contributors remain visible as distinct pieces, while shared infrastructure holds the project together. The article connects that community account to production use through cBioPortal at Memorial Sloan Kettering, where moving heavy filtering into ClickHouse SQL made relevant paths about ten times faster, changing waits from minutes to seconds and supporting continued exploration. It also describes a demonstration built from bare-clone git history, one month of GH Archive events, and the shipped system.contributors table, all queried in ClickHouse. The account reports 100,000 issues and pull requests crossed on March 19, 2026, with 83% of issues and 99% of pull requests resolved at the time of the talk, and presents contributor credit and repair as operating parts of the project.


### [Speculation Is All You Need](https://yomu.fyi/post/speculation-is-all-you-need.md)
- Company: [Modal](https://yomu.fyi/company/modal.md)
- Published: Jun 19, 2026
- Type: Explainer

Speculative decoding is presented as the most important optimization for LLM inference, delivering speedups of 2x-3x rather than small percentage gains from kernel tuning. The technique accelerates the decode phase by using a lightweight draft model to generate candidate tokens that the target model processes in parallel, with lossless resampling. The authors released DFlash speculators for multiple Qwen models, achieving an additional 5-20% speedup over existing baselines, and worked with SGLang to integrate them. On a B200 node, the Qwen 3.5 122B-A10B model with speculation reaches over 1000 tok/s at concurrency 1, compared to 250 tok/s without speculation, demonstrating a 4x speedup. Training these speculators is simplified because the data-generating process is the target model itself, making data collection trivial, and the post envisions a flywheel where custom speculators and distillation enable continuous improvement in latency, cost, and quality for self-hosted inference.


### [Palana (Part 1): Why Grab built a secure platform for autonomous AI Agents](https://yomu.fyi/post/palana-part-1-why-grab-built-a-secure-platform-for-autonomous-ai-agent.md)
- Company: [Grab](https://yomu.fyi/company/grab.md)
- Author: Kevin Littlejohn
- Published: Jun 19, 2026
- Type: Explainer

Palana is Grab’s Kubernetes-native platform for running autonomous and semi-autonomous agents with isolation, controlled access, and operational oversight. The post describes why laptop-based tools and simply running agents in containers do not adequately address persistent state, identity, credentials, network access, auditability, and emergency control. Its architecture gives each agent a namespace, service account, storage, network policy, and Vault scope, while Envoy, ext-authz, and OPA mediate and log HTTP(S) egress; proxy-only secrets keep underlying credentials out of agent processes. A portal and pcli manage lifecycle, and external kill switches and idle shutdown provide controls outside the agent. Palana is used for development environments, Slack automation, framework testing, and long-running internal workloads, with deeper architecture details reserved for Part 2.


### [Beyond the warehouse: How METRO Markets built a do-it-all data platform on ClickHouse Cloud](https://yomu.fyi/post/beyond-the-warehouse-how-metro-markets-built-a-do-it-all-data-platform.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Jun 18, 2026
- Type: Problem & solution

METRO Markets outgrew its self-hosted Impala and Kudu-based Hadoop stack as the marketplace expanded, with parallel stores, inconsistent reporting, and too much maintenance burdening a lean data team. They evaluated BigQuery, Snowflake, and ClickHouse against production queries, finding faster ClickHouse performance, including one response falling from four seconds to under 200 milliseconds, while its pricing supported more predictable costs. Airbyte moves CDC data from MySQL and Postgres into ClickHouse; ReplacingMergeTree handles deduplication during background merges, and BigQuery-hosted Google Analytics data enters through cloud storage and external tables. The resulting warehouse consolidates company data and supports seller analytics, credit risk features through Query API endpoints, observability, and emerging AI use cases, while teams query a shared dataset through compatible tools; planned Kafka and Flink integration would extend it to streaming workloads.


### [Data scientists: Powering the future of AI and analytics](https://yomu.fyi/post/data-scientists-powering-the-future-of-ai-and-analytics.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Databricks Staff
- Published: Jun 18, 2026
- Type: Explainer

Data scientists connect statistics, programming, and domain knowledge to turn raw data into models, recommendations, and decisions with business consequences. The role now extends beyond classical modeling to large language models, generative AI applications, agentic systems, and production workflows involving deployment, monitoring, and retraining. Modern practice combines Python, SQL, and libraries such as scikit-learn, PyTorch, Spark, and MLflow with data engineering basics, communication, and domain expertise. Data scientists contribute across problem framing, data access, preparation, feature engineering, experimentation, deployment, and lifecycle monitoring, with governed access and lineage helping align training data with production data. The article concludes that AI assistants and agents can automate routine work, but human judgment remains necessary for trustworthy evaluation, business framing, and actionable recommendations.


### [Why everyone is talking about real-time analytics (a note from “the yellow company”)](https://yomu.fyi/post/why-everyone-is-talking-about-real-time-analytics-a-note-from-the-yell.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Jun 18, 2026
- Type: Explainer

Real-time analytics is presented as a foundational workload for customer-facing analytics, observability, fraud detection, operational applications, and AI agents rather than a niche use case. The discussion argues that performance claims require open, transparent, reproducible benchmarks that disclose methodology, datasets, queries, results, and operating conditions, including continuous ingestion, concurrency, memory pressure, and fresh data. A real-time database should support queryable data within milliseconds to a couple of seconds, incremental transformations, bounded tail latency as writes increase, configurable read-time versus write-time work, unified support for text, vector, JSON, and structured analytics, and efficiency as workload scales. The article connects renewed attention to agentic workloads, whose continuous, high-volume querying makes low latency, concurrency, and fresh context increasingly necessary, and calls for shared standards beyond a single latency number.


### [MosaicLeaks: Can your research agent keep a secret?](https://yomu.fyi/post/mosaicleaks-can-your-research-agent-keep-a-secret.md)
- Company: [Hugging Face](https://yomu.fyi/company/hugging-face.md)
- Author: Alexander Gurung, Rafael Pardinas
- Published: Jun 18, 2026
- Type: Benchmark

MosaicLeaks examines privacy leakage in deep-research agents that combine private enterprise documents with external web retrieval. Queries that appear harmless individually can reveal sensitive facts when an observer combines them over multiple hops, producing intent, answer, or full-information leakage. The benchmark contains 1,001 multi-hop chains interleaving local and web questions, and compares baseline behavior with task-only reinforcement learning and Privacy-Aware Deep Research (PA-DR). Task-only training raises strict chain success from 48.7% to 59.3% but increases answer/full-information leakage from 34.0% to 51.7%, whereas PA-DR reaches 58.7% success with 9.9% leakage by rewarding stage-specific decisions and penalizing query-level privacy risk. The evaluation is controlled, using synthetic enterprise documents, a fixed web corpus, three company contexts, and one multi-hop question-answering harness.


### [Conversation design: How to make your AI Agent communicate like your team](https://yomu.fyi/post/conversation-design-how-to-make-your-ai-agent-communicate-like-your-te.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Author: Fred Walton
- Published: Jun 18, 2026
- Type: Tutorial

AI agents need deliberate conversation design to communicate effectively with customers, covering tone, response structure, handoffs, interaction flow, and response quality. The post argues that without an explicit owner, an agent may over-explain, sound flat during frustration, or escalate too late, undermining trust and prompting customers to seek human help. It recommends defining a concise voice reference, adapting register to the situation, matching detail to the question, supporting customer-led topic changes, designing informative handoffs and follow-ups, and keeping behavioral instructions separate from knowledge-base content. Teams can begin without a dedicated hire by naming an owner, selecting a poorly performing conversation type, auditing instructions, and fixing the worst handoff first. At Fin, an A/B test raised CSAT from 72.8% to 78.4%.


### [Appcues delivers personalized customer engagement with ClickHouse Cloud](https://yomu.fyi/post/appcues-delivers-personalized-customer-engagement-with-clickhouse-clou.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Jun 18, 2026
- Type: Problem & solution

Appcues replaced an analytics stack that included Snowflake and Airflow after rising scale pushed queries to 20 seconds or more and limited reports to 10-minute windows. The company evaluated ClickHouse Cloud on AWS for real-time segmentation, exporting Snowflake data to Parquet in S3 and testing complex email segments with nested conditions, historical events, and negative logic. Production events now pass through Kafka and a clickwriter consumer, while a clickclient library built on Elixir’s Ecto generates controlled ClickHouse queries; SharedReplacingMergeTree, table engines, and materialized views were tuned during a one-year migration. Across 1.31 PB and 410 billion events, P95 queries fell below two seconds, ingestion latency dropped to about five seconds, and analytics costs decreased 23%, while new funnel reports and AI-powered insights were added.


### [Data Pipeline Best Practices: Architecture, Modern Pipelines, and Deployment](https://yomu.fyi/post/data-pipeline-best-practices-architecture-modern-pipelines-and-deploym.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Databricks Staff
- Published: Jun 18, 2026
- Type: Tutorial

Modern data pipelines move raw data from source systems through transformation and storage to downstream consumers, with batch, streaming, or hybrid operation selected according to latency needs. The guidance places service-level agreements first, defining acceptable latency, uptime, and error rates before architecture choices, and compares ETL, ELT, and zero-ETL patterns. It recommends immutable raw landing zones, CDC for transactional sources, schema registries, event replay, incremental loads, and idempotent writes using techniques such as MERGE operations. Performance and reliability practices include partitioning, clustering, data-quality checks, observability, automated CI/CD testing, and cost controls such as autoscaling and storage tiering. Adoption guidance advises piloting a representative pipeline, measuring telemetry and cost, then iterating through regular architecture reviews.


### [What's new in Postgres Managed by ClickHouse: RBAC, Terraform, ClickPipes, extensions, and more](https://yomu.fyi/post/what-s-new-in-postgres-managed-by-clickhouse-rbac-terraform-clickpipes.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Jun 18, 2026
- Type: Announcement

Postgres managed by ClickHouse, which entered public beta in May, received a broad update covering console operations, per-service RBAC, Terraform, Stripe provisioning, ClickPipes migrations, billing, capacity reservations, and extensions. The redesigned console adds service health, resource, and query views, while RBAC provides View and Manage roles across the console and public REST API; the alpha Terraform provider covers lifecycle operations including resizing, HA, replicas, restore, and password rotation. Postgres-to-Postgres ClickPipes now automate schema migration, usage is integrated into ClickHouse Cloud’s metering and billing, and AWS capacity reservations are allocated dynamically across availability zones. Underneath, pg\_clickhouse and pg\_stat\_ch moved to the header-only clickhouse-c library, removing a C++ exception conflict, using Postgres memory contexts, and reducing the x86-64 Linux extension binary from 4.9 MB to 1.4 MB; the update shipped less than a month after beta, with Terraform and extensions still evolving.


### [How Stagwell built privacy-safe ID matching on Databricks](https://yomu.fyi/post/how-stagwell-built-privacy-safe-id-matching-on-databricks.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Sridhar Sundaresan, Suvan Kaul
- Published: Jun 18, 2026
- Type: Explainer

Stagwell built a Databricks Marketplace App to let brands match first-party records against its Identity Spine without sending raw customer data outside their own workspaces. It combines Databricks Clean Rooms, Unity Catalog, Jobs and Notebooks, Delta Sharing, and a React/Express interface. Workspace OAuth and On-Behalf-Of authorization enforce the user's Unity Catalog permissions, while separate service principals and a scoped personal access token support app and clean-room operations. Within the clean room, a packaged notebook joins brand data with the Identity Spine, resolves multiple identifiers, and computes match rates, coverage metrics, and household and consumer IDs; results include aggregated audience insights for activation, while raw customer data and proprietary matching code remain separated.


### [Building a SQL ETL Pipeline: The Complete Guide for Data Engineers](https://yomu.fyi/post/building-a-sql-etl-pipeline-the-complete-guide-for-data-engineers.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Databricks Staff
- Published: Jun 18, 2026
- Type: Tutorial

SQL ETL pipelines are presented as repeatable workflows that extract data from sources, transform it, and load it into warehouses, lakes, or lakehouses for analysis and machine-learning use. The guide addresses source connectivity, extraction patterns, transformation logic, loading targets, governance, performance, testing, and operational design, while contrasting ETL with ELT and broader data pipelines. It explains that SQL can serve as the primary implementation language for transformations and load operations, with techniques including JOIN and GROUP BY, window functions, MERGE upserts, and deduplication with ROW\_NUMBER() or DISTINCT. It also covers full versus incremental extraction, batch and streaming needs, schema-on-write versus schema-on-read, and layered validation using row counts, checksums, business rules, and schema-drift monitoring.


### [What is Artificial Intelligence (AI)?](https://yomu.fyi/post/what-is-artificial-intelligence-ai.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Databricks Staff
- Published: Jun 18, 2026
- Type: Explainer

Artificial intelligence (AI) is a branch of computer science that enables machines to perform tasks associated with human intelligence, including learning, reasoning, pattern recognition and decision-making. Modern AI generally learns patterns from large datasets, tunes internal weights and parameters during training, evaluates outputs on held-out data, and applies the resulting model during inference to classify, predict, generate content or trigger actions. Most organizations fine-tune existing foundation models rather than train from scratch, while output quality remains dependent on the completeness, bias and quality of training data. The page separates reactive machines and limited memory from theoretical theory of mind and self-aware systems, and distinguishes today’s narrow AI from theoretical general AI and superintelligence. It also describes generative AI, common applications, risks including hallucinations, bias, privacy and security gaps, and governance, concluding that practical adoption depends on real problems, trusted data and responsible oversight.


### [Data Engineering for AI: A Practical Guide for Data Professionals](https://yomu.fyi/post/data-engineering-for-ai-a-practical-guide-for-data-professionals.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Databricks Staff
- Published: Jun 18, 2026
- Type: Explainer

Data engineering for AI extends traditional ETL by adding requirements for model-ready data, unstructured inputs, feature engineering, governance, and production monitoring. The guide addresses data professionals building or scaling AI infrastructure, covering ingestion, architecture, data quality, privacy compliance, generative AI, and career development. It emphasizes shared feature schemas, pipeline data contracts, lineage, statistical validation, drift detection, and PII stripping or anonymization as responsibilities shared across data engineering and data science. For generative AI systems, it describes preparing RAG pipelines by ingesting and chunking documents, creating vector embeddings, and indexing them for semantic retrieval, while evaluating vector databases for latency, scale, and integration. It concludes that reliable AI depends on fresh, accurate, compliant data and ongoing operational and architectural review.


### [Data Warehouse Types: A Complete Guide to Architectures and Use Cases](https://yomu.fyi/post/data-warehouse-types-a-complete-guide-to-architectures-and-use-cases.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Databricks Staff
- Published: Jun 18, 2026
- Type: Explainer

A data warehouse is a centralized repository for structured data, supporting complex queries, reporting, and business intelligence rather than transaction processing. The guide compares architectures by scale, latency, cost, scope, ownership, and governance. Enterprise data warehouses integrate organization-wide sources through ETL, apply cleansing and validation, and provide a governed source of truth, while data marts focus on departmental analysis and may be dependent or independent. Operational Data Stores replicate current or recent operational data for reporting refreshed from minutes to hours, whereas virtual, cloud, hybrid, and lakehouse designs trade physical consolidation, scalability, flexibility, and governance differently. The comparison also frames lakehouses as combining open-format data lake flexibility with warehouse-style governance and transactional reliability.


### [The new bottleneck](https://yomu.fyi/post/the-new-bottleneck.md)
- Company: [Stack Overflow](https://yomu.fyi/company/stack-overflow.md)
- Author: Eira May
- Published: Jun 18, 2026
- Type: Problem & solution

AI coding tools have significantly lowered the cost of generating software, yet many engineering organizations fail to realize overall delivery speed improvements. Applying the Theory of Constraints reveals that eliminating code production as a bottleneck shifts inventory directly into surrounding legacy processes that remain unadjusted. New friction points consistently emerge across underspecified requirements, prolonged design handoff gates, senior engineer review capacity, and external sign-offs from legal or security. Organizations can address these blockers by interrogating legacy agile ceremonies checkpoint by checkpoint to determine if their original constraints still exist. Practical remedies include adopting real-time co-development between product and engineering, treating initial designs as fluid starting points, and restructuring processes around running rapid, high-volume experiments.


### [What is Row-Level Security?](https://yomu.fyi/post/what-is-row-level-security.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Databricks Staff
- Published: Jun 18, 2026
- Type: Explainer

Row-level security (RLS) is a database access control that filters which table rows a user may read or change according to identity, role, or session context. It supports multi-tenant SaaS, regional segregation, departmental access, compliance, healthcare, and partner use cases, while typically layering table-level grants with column-level security or data masking. The database applies a policy or predicate automatically at query time across BI dashboards, notebooks, ad-hoc SQL, APIs, and third-party tools, with separate USING and WITH CHECK rules for reads and writes. On Databricks, Unity Catalog row filters use SQL user-defined functions and apply across Databricks SQL, notebooks, jobs, and connected BI tools. The source recommends simple predicates, indexed keying columns, identity-based testing, and explicit enforcement for both reads and writes.


[Newer posts](https://yomu.fyi/posts/page/108.md) · [Older posts](https://yomu.fyi/posts/page/110.md)