Loading…
Browse by type
Explainer reads
Explainer posts on Yomu, summarised newest first.
- 1,376 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
Red Hat OpenShift Virtualization memory management overview
The post overviews recent memory management evolutions in Red Hat OpenShift Virtualization, spanning from the Linux kernel to the orchestration planes. Historically, the platform uses a 1:1 memory request mapping, but data shows most VMs use only about 20% of allocated RAM, creating a delta that scales infrastructure with workload definitions rather than demand. Node-level optimizations include free page reporting (FPR), which asynchronously recovers pages freed by the guest OS without forcing allocation like ballooning, and KSM zero pages for guest-agnostic deduplication of zero-filled memory. At the cluster level, Multi-Gen LRU integrated with control groups enables swapping to fast secondary NVMe storage, and a PSI-aware descheduler proactively migrates VMs to relieve memory pressure across nodes. OpenShift Virtualization 4.22 provides an autopilot feature that automates configuration for generally available memory optimizations, while developer preview capabilities require manual opt-in activation by default.
What Makes a Great KotlinConf Proposal?
The KotlinConf 2027 Call for Papers is open, and the post offers guidance for crafting a strong proposal, emphasizing that a valuable talk can come from a simple lesson learned rather than a groundbreaking discovery. Reviewers first notice the overall care, including a clear title and focused abstract, and they can detect AI-generated content, so authenticity and a personal voice are crucial. A good proposal starts with a central story that identifies a problem, what was tried, and what was learned, even from a small project, and it should be tested with colleagues. The title should communicate the topic and benefit, avoiding vagueness, while the abstract should provide two to three paragraphs of meaningful detail that outline the talk’s journey and include concrete takeaways. The post advises choosing the right format between lightning and regular sessions, and reviewing the proposal for clarity and authenticity before submitting.
Three layers, one repo: a tour of google/adk-recipes
The google/adk-recipes repository serves as the single source of truth for ADK content across Google Cloud’s Agent Platform, including the Agents CLI, Agent Garden, and Gemini Enterprise app. It is organized into three top-level folders: core/ with reference patterns curated by the Agents CLI and DevRel teams, plugins/ with installable vertical skills packaged as Plugin Recipes conforming to the Agent Plugins v1.0.0 spec, and contrib/ with end-to-end deployable services in five languages. Every recipe ships a validated manifest.yaml and an AGENTS.md written primarily for AI coding assistants, and CI enforces the standards on every pull request. The core/ layer features Horizon, a reference harness for long-horizon memory agents that handles cross-session memory, per-user sandboxing, guardrails, and multi-step task orchestration. The retail Plugin Recipe includes product-search and virtual-tryon skills using Vector Search 2.0 and Gemini models, with deployable counterparts in contrib/ that can be surfaced on five deployment personas.
OLTP vs. OLAP: Choosing Between Transactional and Analytical Databases
OLTP handles high-volume, low-latency transactions on current operational data for online banking, e-commerce, and inventory, while OLAP handles complex analytical queries on large historical datasets for financial analysis and business intelligence. OLTP databases ensure data integrity through ACID compliance and use normalized row-oriented tables; OLAP systems use denormalized dimensional models and columnar storage for efficient scans and aggregations. Data pipelines such as ETL or CDC tools like Debezium connect OLTP and OLAP systems, but latency and pipeline complexity rise with analytical freshness requirements. For mixed workloads, HTAP or lakehouse architectures can reduce synchronization overhead and analytical lag. The choice between OLTP and OLAP depends on the workload’s read-write pattern, latency needs, and data volume, with TPC-C and TPC-H as reference benchmarks.
What is HTAP? A plain-English guide to hybrid transactional/analytical processing
HTAP (Hybrid Transactional/Analytical Processing) brings transaction processing and analytics together so applications can run analytical queries on current operational data without waiting for batch data pipelines. This architecture addresses the delay caused by traditional separation of OLTP and OLAP systems, where data had to be copied into a data warehouse before analysis. HTAP designs vary: converged systems use a single database engine for both workloads, while composed systems use separate engines connected through shared storage or replication. The central challenge is providing analytical access to fresh operational data without compromising transactional performance and reliability. For workloads needing independent scaling, Lake Transactional/Analytical Processing (LTAP) offers a unified storage layer under one governance model, reducing the need for change data capture and replication pipelines.
Everyone's adopting AI agents. Almost no one can prove the ROI. Here's why
Many organizations are quickly adopting AI agents, yet almost none can convincingly demonstrate the return on investment due to a mismatch between purchasing decisions and actual usage. This gap arises because executives buy AI out of fear of being left behind, not from validated ROI studies, and teams measure productivity using speed metrics that miss the broader picture. True productivity from agents is about automating routine, schedulable tasks so human experts can devote energy to judgment calls and creative work, provided quality is maintained alongside efficiency. Without rich business context like institutional knowledge, local regulations, and historical data, an AI agent cannot deliver meaningful work, no matter how fast it executes generic instructions. The most frequent mistake is scaling prematurely trying to roll out broadly after a few promising demos, without ensuring the necessary iteration, infrastructure, and readiness for reliable, quality outcomes at scale.
Your next job doesn’t have a title yet: Emerging role skills Q&A with Corey Hymel of Andela
Corey Hymel, head of research at Andela, analyzed nearly 50,000 job postings to identify emerging skill bundles that precede formal job titles. The research found AI is creating niche skill sets, not turning everyone into generalists, with roles like LLM application engineer building on top of APIs, FinOps reliability engineer managing consumption-based costs, and docs-as-code engineer constructing context for AI models. Hymel described “bleed roles” where skills merge between adjacent specialties, such as front-end product engineers stretching into product management. The data also showed developer attitudes toward AI tooling vary, with some hand-coding for accountability while others ship code that passes tests without concern. Hymel advises engineers to understand where trends are heading and invest effort to prepare for roles that are morphing but not yet commonly titled, emphasizing the importance of strategic upskilling.
vLLM vs. SGLang: Choosing the right inference engine for your workload
Open weight models now process nearly 80% of production tokens on Vercel’s AI Gateway, up from under 10% in December 2025, and OpenRouter shows a similar climb. This surge drives teams to consider self-hosting via inference engines like vLLM and SGLang, since swapping backends usually only requires a new base URL for an OpenAI-compatible API. vLLM’s PagedAttention, introduced by UC Berkeley in 2023, splits the KV cache into fixed-size blocks to eliminate wasted contiguous memory reservation and increase GPU throughput. SGLang’s RadixAttention, from LMSYS in January 2024, stores computed KV cache in a radix tree keyed by token prefix for reuse across related requests like multi-turn chat and agents. Independent benchmarks from Modal show comparable performance on random prompts without prefix sharing, indicating that workload type and hardware should guide engine choice.
How Cloud-Based Agent Sandboxing Works in Air
AI agents require sandboxing to restrict file, network, and system access, preventing unintended modifications and data leakage. The post categorizes five agent execution modes into local (workspace, git worktree) and remote (SSH, Docker, Cloud), with remote modes providing stronger isolation by default. In JetBrains Air, each cloud agent task runs in its own VM with the agent inside a Docker container, and all network connections are routed through a proxy that allows only trusted domains by default. Secrets are stored encrypted and exposed as environment variables, and the agent operates within the developer’s repository permissions. Cloud-based execution reduces local setup requirements and gives organizations control over network access policies, with cloud agents currently available to organizational users via Air in IDEs and Air Teams.
KotlinConf Recap: Lessons from Verifone’s Architect on Kotlin in Mission-Critical Payments
Verifone architect Yuri Geronimus presented at KotlinConf 2026 on using Kotlin’s type system to enforce payment specifications at compile time. He described six incident patterns where a single misused word caused outages, compliance failures, or financial loss, including a terminal fleet outage from a nullable mandatory field. His method uses value classes for spec nouns, validate factories at boundaries, non-null types, masked sensitive data by default, and state-specific classes to make illegal states unrepresentable. Geronimus advocates incremental migration from legacy Java and C++ systems using four parallel tracks rather than a rewrite, noting that payment terminals must operate offline for up to 40 days by regulation. The approach shifts reliability from developer discipline to compiler enforcement, enabling engineers to speak the business language and propose regulatory changes.
Code-Switching Detection via Language-Selective Dimensions in Speech Foundation Models
Code-switching, the alternation between languages in a single utterance, is common in multilingual speech but underrepresented in training corpora for speech models. To address this, a lightweight method detects code-switching directly from speech without requiring multilingual transcriptions. The approach leverages language-selective dimensions in pretrained speech encoders by identifying hidden-state dimensions selective to each language from monolingual recordings and aggregating frame-level activations to predict code-switching. On the CS-FLEURS dataset covering 14 language pairs, the Whisper-small encoder achieves a mean F1 of 0.798, outperforming a CNN baseline (0.776) and a HuBERT linear baseline (0.751). These results show that pretrained speech encoders inherently encode the information necessary for code-switching detection, offering a scalable tool for building more representative multilingual corpora.
Why Your Sandbox Never Quite Matches Production (And Why That's Fine)
The gap between sandbox and production environments is structural and inevitable because they change on different schedules with different triggers. Infrastructure divergence rarely affects what integration tests catch, but behavioral contract drift—when simulated upstream responses no longer match real ones—causes tests to pass while production fails. The most effective teams connect simulation updates to upstream deployment events rather than to test failures, using observation-based tools like Keploy that capture real HTTP traffic to keep simulations current. Full production parity is not the goal; targeted accuracy for the specific behavioral contracts that integration tests validate is sufficient to catch the failures that matter most in distributed systems. The sandbox covers what it can, production reveals what it cannot, and the maintenance work is keeping the sandbox’s coverage accurate within its boundary, not expanding it to match production exactly.
Redesigning source control at Anthropic
At Anthropic, Claude’s ability to iterate on code at high speed has caused git-based source control to become the bottleneck in their development workflow. To handle the growth from 2,500 to over 30,000 daily code merges, the team built Scion, an in-house version control system, fully migrating their monorepo from git in five months. Scion diverges from git by assuming clients are always online, shifting computation to the server, and using horizontally scalable data structures without any fully materialized copy of the repository. The system stores changes as entries in a write-ahead log, supports sparse and virtualized checkouts, and enables cheap, lock-free commits that scale with change size rather than repository size. Anthropic shares Scion’s design principles to help the broader ecosystem prepare for AI-driven scaling challenges, noting that similar pressure points will emerge for other organizations as AI coding tools become more common.
Under the hood, off the hot path: How D1 scales to millions of databases
D1, Cloudflare’s serverless SQLite database, has seen 15x growth in live databases over the past year and scales by keeping query execution on the edge in Durable Objects, separate from the control plane’s metadata operations. The control plane uses an Edge API Worker with Hyperdrive to access Postgres clusters for transactional metadata, while Workers KV caches database-to-Durable-Object mappings for fast edge lookups. Database creation completes in about 1.6 seconds by generating a Durable Object ID, persisting metadata to Postgres, and storing the mapping in Workers KV, with the Durable Object lazily initialized on first query. Storage usage enforcement uses atomic counters in Workers KV that are checked locally on each query and updated asynchronously after execution, avoiding any central database round trip during the query. Precomputed aggregations for billing are stored in ClickHouse, and guiding principles such as eventual consistency and idempotency further reduce reliance on centralized components.
Behind the messenger: making messaging human - The Intercom Blog
Intercom redesigned its messenger to make business communication personal, moving away from the anonymity of the early internet. The post argues that sharing real names, faces, and job titles builds trust, as user testing showed customers repeating the names of the reps they messaged. System-generated text like active status, location, and local time that cannot be changed adds authenticity and helps users understand the asynchronous nature of the system. The post recounts an incident where a customer doubted a rep’s real name, highlighting the need for transparency, and notes that job titles prevent white lies like claiming to pass feedback to a product team when the rep is on that team. The post concludes that these small details together build trust, leading to customer loyalty and forgiveness when things go wrong, and that users initially don’t expect this information but quickly come to expect it everywhere.
Basecamp's Jason Fried on product strategy - The Intercom Blog
Jason Fried, co-founder of Basecamp, discusses the company’s approach to product strategy, including when to undertake a major product overhaul. Basecamp releases ground-up versions every few years when incremental updates reach a local maximum, and it supports older versions indefinitely to avoid forcing customers onto its schedule. Fried argues that a chat-first communication mindset can be toxic and that Basecamp’s tools are designed for asynchronous, organized communication rather than real-time chat. Despite generating tens of millions in revenue and profits, Basecamp deliberately keeps its team small to avoid the pressure of a large organization and to focus on creating great work. Fried advocates for careful growth over rapid scaling, a philosophy he plans to explore in a future book titled “Regrow.”
Facebook's Julie Zhuo on product design - The Intercom Blog
Julie Zhuo, Facebook’s VP of Product Design, recounts her evolution from engineering intern to leading design for the core Facebook app, including News Feed and the Like button. She defines good design as an experience that is enjoyable, useful, easy, and accessible, noting that adding functionality without increasing complexity is a persistent challenge. There is no fixed ratio of designers to engineers; the ideal mix depends on the stage of achieving product-market fit. Effective design principles should be controversial, as they articulate why a company made a particular choice over alternatives. When competing products offer similar utility and ease, the ultimate differentiator is the emotional response the product evokes in the user.
Bob Moesta on Jobs-to-be-Done - The Intercom Blog
Bob Moesta, a principal architect of the Jobs-to-be-Done framework, explains that JTBD interviews focus on uncovering the actions and progress a buyer is trying to make, not opinions or product features. He describes the key forces driving customer switching—push, pull, anxiety, and habit—and notes that innovation opportunities lie at the edge where people want to be better, not with habitual users. Moesta introduces the concepts of big hire (purchase) and little hire (actual use), emphasizing that value is delivered in the latter and that both must be designed for. He addresses zombie revenue, which can arise when customers move on after the job is done, don’t understand the product, or when the product serves a different job than intended. For startups new to JTBD, Moesta advises removing their product from the interview equation and starting with competitor customers to understand the context and outcome independently of the product.
Clearleft's Andy Budd on designing for users - The Intercom Blog
Andy Budd, co-founder of Clearleft, discusses why design is a critical differentiator for startups, noting that companies like Slack and Dropbox succeeded through superior user experience rather than being first to market. He advises hiring the best designers you can afford early to solve existential business problems, then bringing in a more junior team to evolve and maintain the product. Consumer expectations for digital design have risen greatly, but startup budgets haven’t kept pace because few designers hold budget-making positions, creating a misalignment. Agile development has a place, but companies must balance it with longer-term systems that make design, technology, and products scalable. For voice-activated interfaces, designers will still need to define decision trees and logic, shifting from graphic design to conversational and personality design, as seen with tools like x.ai’s Amy.
Tomasz Tunguz on Venture Capital - The Intercom Blog
Tomasz Tunguz, a partner at Redpoint Ventures, discusses the key metrics he looks for in potential investments, including sustainable competitive differentiators and revenue benchmarks. He identifies three types of sustainable competitive advantage: a founder’s market discovery, difficult-to-replicate technology, or a new distribution mechanism. For Series A investments, he typically partners with companies at $50,000-100,000 MRR, but also invests in pre-revenue ideas, noting that 27% of Series A rounds had no revenue. He looks for short sale cycles under 45 days and negative net churn as signs of product-market fit, and advises founders to always have a plan to reach profitability on current cash. Investors view businesses as collections of risk, and founders should address how they will mitigate major risks in their pitch.
Top topics
- Architecture834
- Performance816
- LLMs668
- Machine Learning622
- Open Source567
- AI Agents559
- AI476
- Developer Experience448
Weekly digest
The best engineering reads, once a week.