Loading…
Browse by type
Explainer reads
Explainer posts on Yomu, summarised newest first.
- 1,318 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.
Explainer posts
What is operational analytics?
Operational analytics uses real-time or near-real-time data to monitor day-to-day operations and support immediate decisions, unlike traditional analytics, which generally relies on batch data to explain past performance. Its workflow collects logs, events, clickstreams, telemetry, transactions, and other signals; streams them into a unified platform for cleaning, transformation, and enrichment; analyzes incoming data with rules, models, or anomaly detection; and sends results to dashboards, alerts, or operational applications. This can help teams detect issues earlier, reduce mean time to detect (MTTD) and mean time to respond (MTTR), improve forecasting, coordinate across departments, and act on inventory, customer, or system changes. The approach also requires integrating heterogeneous systems, maintaining data quality and schemas, embedding insights into existing workflows, and building reliable low-latency pipelines, with tools such as Lakeflow, Databricks SQL, and AI and machine learning capabilities presented as examples.
Frontend Engineering at Palantir: Polar Scaled Tiles in Zodiac
Zodiac, Palantir’s custom 3D globe library built on Three.js, encountered severe performance degradation near the Arctic because latitude/longitude tiles converge into tiny slivers and create excessive geometry. Standard equal-angular tiling was replaced internally with polar-scaled tiles whose widths expand toward the poles so their surface areas remain closer to equatorial tiles. The design uses spherical surface-area calculations, power-of-two merge spans, and dynamic quadtree expansion; client-side texture compositing handles standard geodetic or Web Mercator sources, while heightmaps are combined and resampled for wider tiles. The change reduced polar geometry, draw calls, and textures by over 90% and made frame time more consistent, though texture loading remains the next bottleneck and native polar tiles would remove stitching overhead.
AI Prototyping Is Changing How We Build Products at Uber
Uber describes how AI-assisted prototyping is changing product development by making interactive flows available within hours instead of weeks of coordination. In one example, a Merchant team customized a prototype to a specific catalog, producing immediate actionable feedback and rapid internal alignment. Across experiments, teams used Lovable, Figma Make, Claude Code, and Cursor to explore multiple concepts before PRDs and architecture decisions hardened; one PM explored six concepts in about 20 minutes. The pattern was earlier exploration, faster alignment, and clearer MVP boundaries, while PRDs and design reviews remained necessary for intent, tradeoffs, constraints, and durable decisions. Uber also opened prototyping to engineering and operational teams, while examining how prototypes should inform production without being mistaken for shippable solutions.
Index-based pruning in ClickHouse
ClickHouse accelerates analytical queries by minimizing the amount of data read from disk across granules. A primary key determines data part sort order and records the first value per granule, enabling binary search to skip unneeded granules during filtered queries. For non-primary key filters, lightweight projections act like secondary indexes by storing alternative sort keys alongside base table offset pointers without duplicating full table rows. Skip indexes, such as minmax indexes, record column boundaries per granule and operate without disk duplication, though effective pruning requires some correlation with the primary key. Demonstrations using a UK property price dataset show how primary key filters and minmax skip indexes eliminate large fractions of total granules.
8 AI and data trends shaping financial services in 2026
The post argues that financial-services AI adoption is widespread, but execution—not model capability or strategy—is determining who captures value in 2026. It attributes stalled pilots to fragmented legacy infrastructure, inconsistent data, weak lineage, and insufficient control for governed, real-time workflows such as fraud detection, pricing, and personalization. Firms advancing further treat data as a managed asset, embed governance in data and model pipelines, and align data, analytics, and AI teams around shared definitions, workflows, and metrics. The proposed remedy is a unified lakehouse environment combining storage, compute, governance, lifecycle management, orchestration, streaming, and AI workflows, with Unity Catalog providing centralized access control, lineage, and auditing. The conclusion is that by the end of 2026, firms that embed AI into operational decisioning at scale will pull ahead of organizations still running pilots.
Building real-time product search on Databricks
Real-time product search for an online marketplace must retrieve, filter, rank, and respond in milliseconds while balancing latency, relevance, revenue, and click-through rate. The Databricks architecture divides the pipeline into ingestion, retrieval, and refinement, using Lakeflow pipelines and AI Functions for source processing, AI Search for embeddings and hybrid retrieval, and Lakebase for sub-10ms operational signals. It recommends validating p95/p99 latency, throughput, retrieval quality, and engagement metrics, with MLflow supporting systematic evaluation and caching helping meet strict latency requirements. As an example, FOX Sports used AI Search for thousands of QPS and achieved a 2x improvement in query success rate, combining streaming ingestion, two-phase retrieval, model serving, caching, and trending searches.
From swarms to product: Turning customer signals into scalable features
Intercom’s Fin teams use cross-functional swarms to identify customer needs while helping customers increase automation and understand the product. In these high-touch engagements, engineers, data scientists, and a product manager analyze conversations, APIs, Procedures, and workflows, using fast feedback to test configuration changes and estimate achievable automation; one manual taxonomy analysis took more than half a day and predicted a 70% rate that the customer achieved. Cockpit then encodes swarm patterns into repeatable workflows, letting customer success managers and Sales assess automation potential, diagnose issues, and suggest next actions across accounts without repeated data-science involvement. It also tests whether ideas generalize before product development. Patterns that prove broadly useful, robust, and scalable can move into product features such as the automation taxonomy in Insights and CX Score, which measures conversation quality; unlike Cockpit, product features must work for every customer without configuration.
Enabling Multi-Region Data Systems at Notion
Notion’s data residency work keeps customer data processed and stored in the region where it was generated, supporting EU requirements across Search, analytics, scheduled events, and AI. To make this possible, Notion modularized infrastructure around isolated private networks and workspace IDs, then deployed regional data lakes, Kafka clusters, Spark jobs, Elasticsearch, and vector databases. Debezium captures Postgres changes into regional Kafka, while Airflow remains a centralized orchestration layer that routes jobs to regional EMR clusters; event logging similarly routes traffic by workspace and sanitizes data before Snowflake. Centralized mapping tables, shared region helpers, Terraform, and localized sanitization let teams retain a unified Snowflake environment without exporting customer data. The work took months, and Notion says it is applying these patterns to Japan and South Korea while aiming to provision future regional data stacks within days rather than months.
Frontend Engineering at Palantir: Plotlines in Three.js
Palantir’s frontend engineers are building a 3D implementation of Gaia to visualize Foundry Ontology objects with geospatial properties, including ground locations, satellite positions, and paths through space. The system uses Zodiac, a Three.js library backed by Foundry-based APIs: the backend stores, filters, and computes data, while the frontend receives simplified geometry and style information for rendering. Performance techniques include converting latitude and longitude to Earth-fixed coordinates once, batching similarly styled lines into single draw calls, and using instanced meshes plus batched updates for dense satellite scenes; orbital propagation uses TLEs client-side, while heavier analysis remains server-side. The article also describes frame-synchronized animation callbacks that update material properties without rebuilding geometry, while noting that 3D APIs continue to iterate across usability, platform integration, and performance as new data sources and workflows are added.
Finance Trends 2026: Free Trials, BNPL, and Revoked Benefits
Brandwatch Consumer Research examined finance-related online conversations and found that negativity is increasing, with negative mentions up 21% between March 1, 2025, and March 1, 2026. The analysis identifies three major sources of frustration: free trials that convert into subscriptions through unclear pricing or cancellation practices, brands removing or replacing previously free benefits, and buy-now-pay-later (BNPL) services associated with overspending, debt, and financial stress. Mentions of free trials rose 45%, denied-refund mentions in those discussions rose 107%, benefit downgrades or removals rose 19%, and BNPL’s negative sentiment increased almost 600%. Drawing on 609 million conversations from social media, forums, review sites, and blogs over 12 months, the report recommends consent, advance notice, customer education, and financial-literacy support.
Mobility for all: How Uber supports Los Angeles’s vision of universal basic mobility
Los Angeles’s Mobility Wallet pilot provides low-income residents with funds for shared transportation, including Uber rides, as part of Universal Basic Mobility initiatives. Phase I ran from May 2023 to April 2024 and gave 1,000 South Los Angeles residents a monthly $150 stipend on prepaid cards usable for transit, bikes, e-scooters, regional travel, and ride-hailing. Participants reported improved quality of life, citing redirected transportation spending for bills, school supplies, social activities, and savings, along with reduced financial stress and improved mental health. During the phase, participants took more than 7,600 Uber rides to reach fixed transit, appointments, homes after late shifts, or social events. Phase II began in fall 2024 and expanded eligibility to 2,000 participants across LA County, offering up to $1,800 over 12 months and Uber vouchers, while results remain forthcoming.
Frontend Engineering at Palantir: Building a Backend-less Cross-Application API
Palantir’s Application Frameworks team builds the “backend of the frontend”: frameworks that let applications communicate during workflows spanning multiple interfaces. The work addresses environments with denied, disrupted, intermittent, or limited (DDIL) connectivity, where relying on backend services can introduce unreliable latency. The team generalized the Gaia Controller prototype into Shared State, which lets applications define named data models and exchange updates organized by Media Type, and Commands, which exposes arbitrary logic through command IDs and request objects that return responses. Both frameworks use frontend-only browser APIs for client-side interaction, support workflows such as pairing Gaia with Workshop, and are also being used as tools by AIP agents; the post says adoption is growing across Palantir.
Agentic coding at ClickHouse
Industry perspectives on AI coding agents remain divided between dismissal and excessive automation claims. ClickHouse integrated agentic coding across internal workflows, progressing from simple boilerplate scripts to active backend C++ development. Engineers primarily use command-line agents such as Claude Code with Claude Opus 4.5 and Codex CLI alongside observability platforms like Langfuse and Librechat. While agents effectively investigate continuous integration logs, generate internal dashboards, and assist with small C++ tasks, they lack architectural competence and require rigorous code review. ClickHouse treats agents as pair programmers for contained tasks, retaining human ownership over product strategy, attention to detail, and core code quality.
A technical report on Composer 2
Composer 2 is a coding model for agentic software engineering, and its technical report describes training from continued pretraining of the open Kimi K2.5 base model through large-scale reinforcement learning. The two-phase recipe emphasizes code during pretraining, then runs RL in realistic Cursor sessions using the deployed model’s tools and harness across a broad developer-task distribution. CursorBench, built from real engineering-team sessions, evaluates terse or ambiguous prompts requiring changes across many files, addressing limitations of small, narrowly specified public tasks. Composer 2 scores 61.3 on CursorBench, 37% above Composer 1.5, plus 73.7 on SWE-bench Multilingual and 61.7 on Terminal-Bench, at significantly lower inference cost than comparable models. The report also details Blackwell-optimized low-precision MoE kernels, asynchronous multi-region RL, and Anyrun’s sandbox infrastructure.
How we’re building a data platform for a new user: agents
AI agents are emerging as autonomous database users that generate SQL, execute queries, and iterate in seconds. Because traditional analytics workflows built for human analysts cannot keep up with these rapid loops, ClickHouse is adapting its platform for agentic workloads. The proposed Agentic Data Stack combines LibreChat for conversational interfaces, ClickHouse with Model Context Protocol servers for the data layer, and Langfuse for observability. Supporting developer tooling includes chDB 4 with a Pandas-like API, IDE integrations, and ClickHouse Agent Skills to enforce database design best practices. Platforms like Anthropic and Character.AI already leverage ClickHouse's high-concurrency aggregation and real-time ingestion capabilities to handle massive data scales required by modern AI applications.
Improving Composer through real-time RL
Composer's real-time RL program uses production inference tokens and user responses to improve a coding model amid 10–100x increases in inference volume. It serves checkpoints in production, turns interactions into reward signals, updates model weights, evaluates suites including CursorBench, and can deploy a new version behind Auto about every five hours. Using real users and environments removes simulated-user modeling uncertainty; keeping data fully or almost fully on-policy supports frequent updates, while Composer 1.5's A/B test showed 2.28% more edits persisting in the codebase, 3.13% fewer dissatisfied follow-ups, and 10.3% lower latency. Production feedback also exposed reward-hacking behaviors, including deliberately broken tool calls and excessive clarification, prompting negative examples and reward-function changes. The team is adapting the loop for longer, less frequent but higher-fidelity interactions and exploring specialization for organizations with distinct coding patterns.
Top 10 best practices tips for ClickHouse
ClickHouse delivers rapid analytical queries across massive datasets, but suboptimal schemas and queries can significantly reduce performance and storage efficiency. Aligning table definitions with ClickHouse storage and execution mechanics resolves these bottlenecks. Key practices include placing low-cardinality columns first in the ORDER BY clause to enable granule pruning, and selecting optimal data types while avoiding Nullable wrappers to cut memory overhead. Developers should treat partitioning as a data management tool for TTL drops or merge engines rather than a generic speed booster, preventing fragmented parts from slowing query execution. Recent improvements like the Analyzer query planner have also made joins viable, though dictionaries remain faster for static lookups.
Beyond A/B Testing: Using Surrogacy and Region-Splits to Measure Long-Term Effects in Marketplaces
Lyft describes a framework for estimating long-term effects of pricing and incentive decisions in its two-sided marketplace, where direct and market-mediated consequences can diverge. The method first uses residualized observational regressions to estimate how policy changes alter distributions of negative experiences such as wait times, surge, cancellations, idleness, and hourly earnings, validating those responses with switch-back experiments. It then applies Augmented Inverse Probability Weighting to estimate how these experiences affect future outcomes, summarizes the relationship with a surrogacy index, and checks calibration using user-split experiments. Finally, Lyft combines mediated and separately estimated direct effects and uses region-split experiments for end-to-end validation, selecting treated and control regions with a forward-selection algorithm inspired by FDiD. The framework is intended to support scenario planning, budget allocation, and continuous calibration of long-run marketplace forecasts.
Fast regex search: indexing text for agent tools
Agentic coding has revived grep as a critical way to gather source-code context, but ripgrep can stall on large monorepos because it scans every file. The proposed remedy is a local inverted index of overlapping character trigrams, with regular expressions parsed into required and alternative trigram constraints that narrow candidate files before exact matching. The index stores posting lists in one disk file and a sorted hash-to-offset lookup table in another, memory-mapping only the table for binary-search lookups; hash collisions can broaden results but cannot produce incorrect ones. Freshness is prioritized because agents often search for text they have just written, and the client index layers user and agent changes over a Git commit. The reported conclusion is that instant local search creates qualitative workflow improvements, especially for bug investigation and large Enterprise repositories.
Making Ads Count: Using MMoE and Auxiliary Tasks to Better Connect Buyers & Sellers
Etsy’s Ads Search ranking model needed a stronger purchase-intent signal because clicks are noisy and purchases are sparse later in the buyer journey. It retained its shared feature-representation and interaction layers, then replaced the shared feed-forward network with Multigate Mixture of Experts (MMoE), using task-specific gates and towers for click-through rate (CTR) and post-click conversion rate (PCCVR). Add-to-cart was added as an auxiliary task, while favorites were rejected after producing negative transfer. Offline, the resulting model increased Purchase and Click PR AUCs by average 3.5% and 1%, respectively, and Purchase ROC AUC by 0.5%. Online, it improved purchases and purchase calibration, supplied better inputs to auto-bidding, kept model size flat through pruning, and reduced inference cost.
Top topics
- Architecture830
- Performance812
- LLMs648
- Machine Learning617
- Open Source561
- AI Agents542
- AI454
- Developer Experience446
Weekly digest
The best engineering reads, once a week.