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
Genesis Workbench: A blueprint for industry AI in life sciences, powered by Databricks and NVIDIA
Genesis Workbench is an open blueprint for a Databricks-native life-sciences application that brings computational drug-discovery stages into one governed workbench. It combines Unity Catalog governance, MLflow tracking, Model Serving, serverless GPU compute, Databricks AI Search, and NVIDIA technologies including CUDA-X libraries, Parabricks, BioNeMo tools, GenMol, and Proteina-Complexa. Independent modules cover genomics, single-cell analysis, large- and small-molecule workflows, and model fine-tuning, with handoffs spanning gene-to-sequence resolution, structure prediction, docking, ADMET, and candidate ranking. A point-and-click React interface supports bench scientists, while declarative workflow generation and MCP exposure let pipelines and external clients use the workbench; inference runs on GPU endpoints inside the governed workspace without runtime external API dependencies. The stated aim is to let teams move from disease hypotheses to ranked therapeutic candidates on their own data, with a roadmap for automated workflow generation, BioNeMo Skills integration, and additional MCP services.
Maximize AI Factory Energy Efficiency Through Full-Stack Inference and Training Optimizations
Power costs comprise up to 40% of AI factory operating expenses, making performance per watt critical within fixed site power limits. Operators maximize throughput by combining architectural enhancements, narrow-precision formats like NVFP4, and mixture-of-experts model designs that activate fewer parameters per token. During distributed LLM training in Megatron-LM, tuning individual GPU speeds along critical execution paths eliminates idle power waste without extending total training time. Additionally, the NVIDIA DSX platform orchestrates dynamic power allocation, 45°C direct-to-chip liquid cooling, and grid integration across racks and facilities. Together, these full-stack optimizations enable performance-optimized AI factories to deliver up to 2.6 times more tokens per second per megawatt.
Build Trust in Agentic AI: From POC to Production
Transitioning autonomous agentic AI systems from sandbox environments to enterprise production exposes a trust gap driven by hallucination, reasoning errors, and financial liability. To mitigate these risks, organizations can implement a proactive four-step framework covering foundations, verification, governance, and business outcomes. The architecture grounds agents using retrieval-augmented generation, short-term memory, long-term procedural memory, and observability traces consolidated on a unified data layer. Active verification computes an Agent Confidence Score alongside a deterministic Business Risk Score to produce an Agent Decision Score governing autonomy levels. Aggregated execution telemetry feeds business observability dashboards that monitor unit economics and enable analytical agents to recommend operational interventions.
Coinbase reduces time from idea to production by 90% with Cursor
Coinbase redesigned its engineering model around agent-first infrastructure rather than retrofitting AI into legacy processes, making time from idea to production its north-star metric. More than 2,400 developers use Cursor; engineers define intent, write requirements for agents, plan work with Plan Mode, delegate implementation, and validate results, often running 5–7 asynchronous agents in parallel. The company reports that some teams cut idea-to-production time from 20 days to less than two days, while first PR creation fell from eight days to under 30 minutes; 75% of PRs are agent-created, and average developers save seven hours of coding weekly. Coinbase also uses smaller working groups, internal champions, speedruns, and Superbuilders to spread these workflows and build tooling.
Guide to Agentic Systems and AI Agents
Agentic AI systems are goal-directed software platforms that perceive context, plan and execute multi-step workflows, and adapt based on outcomes with minimal human intervention. The guide distinguishes them from traditional and generative AI, defining agents, broader system architecture, and the role of LLMs as reasoning cores connected to memory, APIs, databases, and other tools. It describes a perceive-reason-act-learn loop, multi-step planning, external tool integration through interfaces such as the Model Context Protocol (MCP), and orchestration patterns for coordinating specialized agents. Production concerns include retries, queues, observability, permissions, privacy, logging, and human escalation, while stated risks include reward-hacking, unintended actions, and explainability gaps. It identifies repetitive, data-rich workflows with clear success criteria and bounded error consequences as the best current enterprise candidates.
Top 10 AI Business Solutions Driving Company Growth
The article identifies ten AI business solution categories presented as growth drivers, while arguing that value is concentrated in workflows where AI changes the economics of work. It frames successful adoption around three conditions: clean, governed data; process-first use-case selection; and governance designed in from the start. Examples include customer-service agents, forecasting, personalization, intelligent process automation, and supply-chain optimization; the text says customer service accounts for 40% of top use cases, while data quality accounts for roughly 75% of what makes an AI solution work. It also describes productivity, automation, and business reimagination as distinct value paths, including a payments-data forecasting product that became an eight- to nine-figure annual revenue stream. The conclusion favors unified platforms that connect data, analytics, AI, governance, and agentic workflows.
What is Vector Search?
Vector search retrieves results by comparing embeddings that represent meaning across text, images, audio, and other content rather than matching exact words. A model creates embeddings, an index stores them for fast similarity search, and a query embedding is matched against the index using nearest-neighbor methods. Exhaustive k-nearest neighbor search can become too slow at millions of items, so production systems commonly use approximate nearest neighbor search, trading some precision for speed. The guide positions vector search behind semantic search, RAG, recommendations, and multimodal or cross-language retrieval, while hybrid search combines dense and sparse vectors, keyword results, metadata filtering, and reranking to improve reliability. Quality depends on embeddings, filters, index freshness, and infrastructure, with vector search requiring more memory and compute; Databricks AI Search is presented as a managed service supporting these capabilities and Unity Catalog governance.
Data Lake vs. Cloud Data Warehouse: A Practical Guide for Data Scientists
The guide contrasts data lakes and cloud data warehouses for storing and querying data at scale. Data lakes retain raw structured, semi-structured, and unstructured data in low-cost object storage with schema-on-read, while warehouses enforce schema-on-write for structured analytical workloads. Lakes fit petabyte-scale machine learning, data science, and undefined future use cases; warehouses fit fast, concurrent SQL for dashboards, reporting, and operational analytics. It describes Bronze, Silver, and Gold zones, with Parquet and ORC supporting columnar scans and open-format portability. For teams combining ML and BI, lakehouses use Delta Lake, Apache Iceberg, or Apache Hudi to add ACID transactions, schema enforcement, and quality monitoring to lake storage without duplication; catalogs, staged checks, and access controls help prevent data swamps.
How Telcos Build Autonomous Networks with Agentic AI
Telecom operators currently operate mostly within Levels 2 and 3 of the TM Forum autonomous networks taxonomy, relying on predefined scripts. Progressing to Levels 4 and 5 demands autonomous systems capable of intent comprehension, real-time telemetry sensing, and cross-domain action coordination. To address this, an autonomy platform architecture combines domain-specific reasoning models, agent harnesses, and isolated sandboxed runtimes. Workflows separate responsibilities among on-demand agents, long-running execution loops, and deep-research multi-agent systems that evaluate ranked remediation paths or design wireless algorithms. Initial experiments in simulated SR-MPLS routing and wireless physical or MAC layer design show autonomous discovery can deliver measurable gains over standard operational and engineering baselines.
DataOps Strategy for Modern Data Engineering
DataOps is presented as a collaborative practice that applies DevOps principles—continuous integration, automated testing, and rapid delivery—to the full data lifecycle, from ingestion and transformation through trusted data-product delivery. It treats data as a continuously delivered product, with technical and non-technical participants sharing an operational cadence to improve quality and shorten time-to-insight. The recommended operating model standardizes source onboarding, enforces schemas at ingestion, uses idempotent jobs, version-controls transformations, and promotes them through tested staging and production environments, with the Bronze, Silver, and Gold layers serving as quality gates. Automated unit, data-contract, and regression tests, alongside observability, anomaly detection, SLAs, lineage, and documented rollback procedures, support reliable delivery and faster incident diagnosis. Organizations with mature DataOps practices report up to 99% fewer data-downtime incidents and 30–50% less reactive maintenance.
The future of observability won’t be one proprietary AI agent. It will be thousands built by teams.
Observability vendors are increasingly betting on a universal SRE agent that combines a platform, telemetry, and natural-language investigation. The post argues that debugging depends on team-specific systems, trusted signals, failure history, runbooks, workflows, and institutional knowledge that cannot be packaged into one vendor’s agent. Agents can compare more time windows and pursue more hypotheses than human investigators, creating demand for low-latency query infrastructure and more complete, high-fidelity historical data. It proposes a more open model in which teams build specialized agents on headless observability foundations, with APIs, data storage, and an observability MCP, while persistent investigation surfaces preserve work for collaboration and reuse. Humans remain responsible for direction, judgment, and action, so the near-term future is presented as human-agent collaboration rather than autonomous incident resolution.
Engineering a Vercel Chat Adapter
Vercel’s Chat SDK supports bots across multiple chat platforms, but those channels can be ephemeral and leave conversations buried in feeds and threads. Email offers a persistent, widely used channel, so Resend built an official adapter that treats email as bidirectional chat. Inbound mail arrives through Resend webhooks and triggers Chat SDK handlers, while outbound messages use the Resend API. The adapter reconstructs threads from In-Reply-To and References headers, tracking message-to-thread mappings in an in-memory Map and generating IDs from the sender address and a SHA-256 prefix of the root Message-ID. It also translates Chat SDK messages, including markdown and CardElement structures, into email HTML and plain-text content through React Email components, trading richer native chat semantics for email’s reach and simpler delivery model.
Extending Stripe’s network with stablecoins
Stripe describes integrating stablecoin settlement into its existing Global Payments and Treasury Network (GPTN), rather than creating a parallel system. GPTN models accounts, wallets, and payment rails as a directed graph, allowing routing, netting, cross-entity settlement, FX, reconciliation, and liquidity management to span fiat and blockchain flows. For a payout, Stripe records a pending stablecoin obligation, Bridge draws from a stablecoin liquidity pool to credit the recipient within seconds to minutes, and fiat replenishment proceeds asynchronously over traditional rails; reverse flows work similarly. A direct mode bypasses the usual few-minute planning cycle for urgent wallet funding, trading netting efficiency for speed, while standard flows continue batching. The live infrastructure handles real traffic, with ongoing work focused on forecast-driven liquidity, faster replenishment through RTP and SEPA Instant, and broader product and corridor coverage.
Palana (Part 2): Architecting isolation, identity, and auditability for AI agents
Palana is Grab’s Kubernetes-native secure execution platform for autonomous AI agents, designed to provide isolated, attributable, and auditable environments. It provisions per-agent namespaces, service accounts, EFS-backed storage, ingress, policies, and proxy-mediated egress, while admission webhooks inject proxy settings and enforce pod restrictions. Human identity remains authoritative for RBAC, while sanitized identifiers are reserved for object names and Vault paths; secrets are split between agent-readable values and proxy-only credentials, and the LLM wrapper derives agent identity from Kubernetes context. Layer 3/4 controls provide containment, Layer 7 OPA-backed proxy policies govern host and method access, and structured signals support audit and idle shutdown that preserves /data and platform state. The production lessons emphasize platform-level controls, a safe self-service path, namespace boundaries, proxy-mediated authentication, and lifecycle management as prerequisites for useful autonomy.
Ten years of open source: a stained-glass view
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
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
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.
Data scientists: Powering the future of AI and analytics
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”)
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.
How Stagwell built privacy-safe ID matching on Databricks
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.
Top topics
- Architecture830
- Performance812
- LLMs648
- Machine Learning617
- Open Source561
- AI Agents542
- AI454
- Developer Experience446
Weekly digest
The best engineering reads, once a week.