Loading…
Browse by type
Explainer reads
Explainer posts on Yomu, summarised newest first.
- 1,381 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
Building AI Literacy: Frameworks, Tools, and Practices
AI literacy is presented as the ability to understand how AI works, use its tools effectively, evaluate outputs critically, and recognize ethical implications. The guide organizes this fluency into functional, critical, and ethical domains, with progression from defining terms and crafting prompts to comparing tools, auditing outputs for bias, and designing human oversight. It explains that large language models generate probable continuations from statistical patterns in training data, so hallucinations and bias require verification against trusted sources rather than assuming factual correctness. For education and organizations, it recommends distributed curriculum or role-specific modules, hands-on assignments, measurable assessment checkpoints, governance policies, internal champions, iterative pilots, and longer-term impact metrics.
AI in supply chain: from demand forecasting to AI agents
AI in supply chain management applies machine learning, generative AI and AI agents to demand forecasting, inventory optimization, supplier-risk assessment and logistics orchestration. It connects ERP records, point-of-sale feeds, supplier communications and external signals to support continuous decision-making rather than periodic planning. The guide maps use cases to required data foundations, covering demand-sensing pilots, warehouse task prioritization, agent guardrails, cross-system APIs and generative-AI grounding. It recommends starting with a product category or region, comparing model output with a baseline, and expanding only when accuracy and bias improve consistently. Reported figures include up to 85% forecast-accuracy improvement, up to 15% lower inventory carrying costs, and 23% lower fulfillment costs among organizations that deployed AI at scale.
AI in healthcare: applications and best practices
Healthcare AI applies artificial intelligence, machine learning, deep learning, and generative AI to clinical, administrative, and research workflows, using patient data, EHRs, medical imaging, and clinical documentation to support decisions and operational efficiency. It distinguishes AI models from algorithms and generative models, and describes supervised classifiers, time-series, natural-language-processing, and computer-vision systems used across healthcare. The data section emphasizes standardized models, consistent coding, interoperability through APIs and FHIR, and unified data lakehouse architecture, noting reported EHR prediction accuracy of 70-72% that varies by condition, data quality, and population. For generative documentation, audio transcription, large language models, templates, and Retrieval-Augmented Generation can draft notes, but clinician review remains required because fluent output may contain factual errors. It also covers imaging AI, privacy practices, FDA and European AI Act obligations, and the expectation that clinical AI will augment rather than replace professional judgment.
AI Applications in Finance: A Practical Use Case Guide
AI in finance spans machine learning, natural language processing, and generative AI for credit scoring, fraud detection, algorithmic trading, finance automation, and decision support across banking, capital markets, and insurance. Finance teams rank use cases by revenue impact, risk reduction, and implementation effort, while data scientists clean and validate the underlying data. Credit scoring can combine traditional and alternative data, with confidence thresholds routing uncertain cases to human underwriters; trading strategies use historical backtests, monitoring, and versioned audit trails. Fraud systems monitor transactions in real time and prioritize alerts, while finance automation uses machine learning, rules-based logic, exception queues, and ERP integration. The guide recommends 90-to-120-day pilots with predefined metrics and ROI measurement before scaling, alongside explainable AI, model governance, and logged decisions for responsible deployment.
No Dumb Questions: What is the AI bottleneck? How does context engineering fix it?
An adoption bottleneck slows artificial intelligence integration because standalone tools lack connectivity with everyday enterprise workflows. While models can draft responses or process text, they fail to access siloed background information from emails, chat channels, and shared documents. Consequently, human users must expend disproportionate effort gathering context, granting tool permissions, and editing preliminary outputs. Michael Foree explains that overcoming this hurdle requires context engineering, where practitioners deliberately observe their own thought processes to identify relevant information sources and filter out distracting data. Testing mock prompts and iteratively refining context architectures allows practitioners to bridge the gap between standalone model capabilities and autonomous task execution.
Agent platform (Part 1): How we help Grab build and run AI agents at scale
Grab’s AI support bot grew from an internal GPT-powered Level-0 service into the foundation for LLM-Kit, an internal framework now used by more than 500 services, alongside over 50 registered remote MCP servers and a company-wide LLM gateway handling billions of tokens monthly. The bot used a single-agent reasoning loop and a tool plane spanning Glean, Kibana, GitLab, Slack, and HTTP plugins, but scaling exposed missing evaluations, fragmented observability, provider-switching friction, and costly production plumbing. LLM-Kit addresses those problems with generated FastAPI services, LangGraph agent templates, OpenTelemetry tracing, configuration and secret-management integrations, evaluation routes, remote MCP tool discovery, and gRPC contracts, clients, health checks, and channel selection. The post concludes that framework concerns became platform concerns at 500 agents, leading to a gateway, remote MCP framework, and evals platform described as the series continues.
How the FDA Built an AI Platform That 85% of Its Staff Now Use Daily
The FDA built ELSA, a generative AI platform for its 16,000 staff, on Halo, a governed Databricks data foundation created to address fragmented systems across eight centers. Those centers had separate chatbots and data stores; consolidating 50 to 60 sources enabled faster sharing, real-time streaming, and centralized access controls through Unity Catalog. Within roughly two months, ELSA adoption rose from less than 1% to 85%, while staff began building hundreds of agents weekly from standard operating procedures, regulatory guidance, and center-specific documents. MCP servers layered over Unity Catalog make governed data and tooling accessible beyond data scientists, and Databricks ML and NLP capabilities through MLflow extracted starting materials and product-supplier-manufacturer relationships from millions of submission pages. A reviewer can now request grounded starting-material information for a drug application in about three minutes instead of days, while the FDA adapts center-specific MCP tools and extends the model across its organization.
Permission isn't purpose: Intent-based authorization in Omnigent
Omnigent’s intent-based authorization addresses a gap in identity-based access control: an agent with valid credentials may follow indirect prompt injections embedded in data and perform authorized actions unrelated to the user’s task. It binds each session to a human-declared purpose and evaluates that intent before every tool call, producing permitted, consent-required, or denied verdicts. In a data-quality example, reading a customers table is allowed, dashboard publication requires approval, and an injected request to grant external access is denied despite the agent’s identity permitting that tool. The intent is fixed at design time for autonomous agents or approved by a human at session start for interactive agents, and cannot be broadened by the agent. Omnigent combines this policy with session-risk scoring and other contextual policies in a single engine where any denial wins.
How we built the new Table of Contents feature
Medium built a new Table of Contents feature after an existing Chrome extension demonstrated demand, while its approach of inserting a static list into post content created revision, maintenance, navigation, and reading-experience problems. The shipped implementation derives a nested list from the rendered post body at runtime: H2 and H3 become top-level entries, H4 headings nest beneath the latest top-level heading, and lead title, subtitle, and kicker are excluded. It appears as a right-margin indicator that scrolls with the reader, highlights the current heading, supports smooth scrolling, and uses a sliding window for posts with many headings. Full-width images receive a translucent background, one-heading posts hide the feature, and mobile needs a separate solution because desktop indicators overlap content; the feature took a couple of days, mostly for UX testing and design iteration.
Why R&D Data Belongs in the Lakehouse - and Why Agents Need It There
cellcentric describes how it built a governed lakehouse foundation for R&D data so industrial AI agents can reason over engineering context, not isolated source-system records. On Azure and Databricks, the Data Hub combines Unity Catalog governance, Lakehouse Federation, Delta Sharing, Declarative Automation Bundles, and an MCP interface for agents. Its Fuel Cell Passport unifies five enterprise systems, models seven hierarchy levels, refreshes daily, and uses a state-based temporal model for point-in-time configuration and rework-history questions. The platform treats context coverage as a data-quality metric, with 27 published products averaging 90% column-comment coverage, while authenticated user identity and Unity Catalog authorization constrain agent access. For many R&D and process-development workflows, work that once took weeks now ships in days, though complex multi-source investigations still require substantial domain review.
Inside NVIDIA Rubin GPU Architecture: Powering the Era of Agentic AI
Agentic artificial intelligence workloads require sustained multistep inference, demanding low per-step latency, high decode throughput, and efficient long-context processing. NVIDIA designed the Rubin GPU to deliver up to ten times more agentic throughput per unit of energy than Blackwell. The hardware combines 336 billion transistors across two dies unified by NV-HBI, up to 288 GB of HBM4 memory providing 22 TB/s peak bandwidth, and the third-generation Transformer Engine reaching up to 50 petaflops of NVFP4 compute. Performance optimizations include inline descriptor updates for the Tensor Memory Accelerator, doubled K-dimension instruction throughput, 3-bit lookup-table weights, and structured 2:4 sparse attention compression. At the rack level, Vera Rubin NVL72 leverages Intelligent Power Smoothing and DSX MaxLPS to enable up to 40% more GPUs within a fixed power budget.
NVIDIA Vera CPU: Olympus Cores Built for Maximum Single-Thread Performance in Agentic AI
Agentic AI workloads shift critical execution paths onto CPUs through sandboxed environments that execute code, invoke tools, and manage runtime states. The NVIDIA Vera CPU addresses these compute requirements via Olympus cores built to maximize single-thread performance and instructions per cycle under full socket load. To handle irregular control flows and pointer-heavy structures, Olympus combines a ten-wide decode engine, neural branch prediction supporting two taken branches per cycle, dependency-breaking acceleration, and dedicated graph prefetchers. Across scale-up systems, dual-socket Vera configurations leverage second-generation NVLink-C2C interconnects to maintain a clean two-NUMA-node topology alongside PCIe 6.4, CXL 3.1, and Arm CCA confidential computing. These architectural choices provide predictable latency and memory bandwidth across highly concurrent reinforcement learning and agent loops.
Scaling Agentic RL: High-Throughput Agentic Training with Tunix
Tunix is presented as a post-training library for scaling agentic reinforcement learning, where multi-turn tool use and environment latency can leave TPUs idle. Its design combines an asyncio-based, high-concurrency trajectory collector with asynchronous vLLM-TPU and SGLang-Jax integration, then streams variable-length trajectories through a producer-consumer queue rather than waiting for a complete synchronous batch. Composable agent and environment abstractions expose APIs for custom tools, benchmarks, and external systems while preserving multi-turn token handling and lifecycle management. Lightweight RL-specific metrics correlate rollout, training, weight synchronization, model-call, and environment stages with TPU timelines, complementing targeted XProf traces. The stated outcome is a more observable pipeline intended to reduce stalls, keep accelerators utilized, and support agentic RL natively in the JAX/TPU ecosystem.
The three ways AI unlocks transformation in Retail, Travel, and Consumer Goods
The piece argues that retail, travel, and consumer-goods companies face one problem in three forms: signals are not trusted, arrive too late, or cost too much to process at scale. It contrasts business intelligence, which depends on structured schemas, predefined questions, and dashboards, with AI systems that read unstructured data, reason probabilistically across signals, and connect decisions to action. Examples include reported improvements from Harmons’ shelf scanning, faster consumer-insight work at a health and hygiene company, and travel applications spanning maintenance, pricing, and concierge services. Its proposed architecture combines broad ingestion and open storage with governance, evaluation, model and agent controls, and applications that operate on a substrate, presenting current, coherent data as the foundation for organizations that can act.
Integrate NVIDIA Omniverse RTX Sensor Simulation Into Existing Apps
NVIDIA Omniverse libraries, included in NVIDIA Agent Toolkit, provide modular components for incorporating physical AI features into current tools and services. As part of this stack, the ovrtx prerelease library offers a lightweight C and Python SDK for real-time RTX sensor simulation and visualization using OpenUSD scenes. Host applications retain architectural and workflow control by stepping the renderer directly from their internal loops. Integration relies on ovstage for shared OpenUSD data management alongside RenderProducts and RenderVars to configure camera, lidar, radar, and semantic segmentation outputs. PTC Onshape Render Studio is exploring ovrtx to embed RTX rendering directly into cloud-native CAD and PDM workflows.
AI Agent Orchestration: A Guide for Enterprise Systems
AI agent orchestration coordinates multiple specialized agents by managing task assignment, shared state, communication, and execution sequencing across complex enterprise workflows. The guide contrasts autonomous agents, which reason about subtasks and adapt to intermediate results, with fixed workflows, and recommends decomposing processes into single-responsibility agents with documented input/output contracts and least-privilege access. It describes centralized, decentralized, hierarchical, hybrid, federated, and emergent patterns, noting that pattern selection trades control, resilience, scalability, and auditability according to risk. Implementation guidance includes assigning human owners, defining accuracy, latency, and escalation targets, establishing failure paths, instrumenting a minimal prototype, and measuring a pilot against documented baseline processes. Organizations using multi-agent systems report 35% faster task completion and a 30% efficiency increase with specialized agents, while high-risk or irreversible actions still require human approval gates and audit trails.
AI Transparency: Governance, Explainability, and Data Practices
AI transparency is presented as the practice of documenting and disclosing an AI system’s data, model behavior, decision-making processes, and accountability so affected stakeholders can evaluate its outputs. The guide distinguishes transparency from explainability, which addresses a specific prediction, and interpretability, which concerns direct access to a model’s internal logic. It recommends maintaining model architecture and version history, algorithms and hyperparameters, training-data provenance, and explainability tooling in a central registry, alongside model cards and data sheets. It also calls for subgroup performance metrics, recurring audits, visible AI disclosures, human-review paths, and incident playbooks covering notification, logs, rollback, remediation, and outcome tracking. The stated goal is durable governance that supports trust, bias detection, regulatory documentation, and accountability across high-stakes and generative-AI deployments.
Run Ray on TPU, Part 1: The foundations
Ray 2.55 makes Google Cloud TPUs a first-class accelerator in Ray, with official APIs, pre-built images, and core-library support rather than the earlier experimental path. The central constraint is TPU slicing: a multi-host workload must land on one intact slice because its hosts communicate through the slice’s ICI (Inter-Chip Interconnect). On GKE, the Ray Operator installs KubeRay and a TPU webhook; the webhook labels hosts, while Ray Core uses those labels to reserve a whole slice atomically through the public slice_placement_group() API, with topology and accelerator version as inputs. The guide shows node selection by TPU generation and topology, a multi-host numOfHosts field, and a RayCluster manifest that brings up one worker per host. Ray AI libraries such as Data, Train, and Serve generally invoke this placement primitive themselves, while direct use targets custom distributed workloads; the API is public but alpha.
Responsible AI: Governance, Principles, and Practical Guide
Responsible AI is presented as a lifecycle-wide practice for designing, developing, deploying, and monitoring AI systems with fairness, transparency, accountability, privacy, safety, and human oversight as requirements. The guide connects technical controls—secure encrypted data pipelines, documented dataset provenance, demographic bias audits, adversarial robustness tests, access controls, and continuous monitoring—with governance mechanisms including named model owners, cross-functional oversight, model-risk assessments, and immutable decision logs. For generative AI, it recommends output policies, training-data leakage testing, guardrails, and red-team testing, while model cards, automated fairness checks, independent audits, and incident response plans support transparency and accountability. Regulatory preparation includes mapping systems to the EU AI Act’s risk categories and documenting design, training data, and intended use; the NIST AI Risk Management Framework and OECD AI Principles are identified as governance references.
Tech builds on AI. Finance protects the margin.
AI-native tech companies must protect unit economics as agents accelerate changes in compute consumption, pricing, and revenue recognition, while gross margins remain below classic software levels. Finance teams built around extracts, spreadsheets, and monthly reconciliation can miss repricing changes, metering errors, and compute-commitment risk. The proposed foundation is an evolving ontology that keeps product, plan, usage, and cost meanings current, with Stripe data entering Unity Catalog through OpenSharing and Lakebase providing transactional Postgres on the lakehouse. Genie One uses that ontology to answer governed, sourced questions about gross margin, consumption revenue at risk, and compute spend, while people retain decision authority. The post describes organizations using Databricks to consolidate reporting, forecasting, workflows, and finance applications, positioning a shared data-and-AI platform as the path from an initial answer to an ongoing finance platform.
Top topics
- Architecture834
- Performance817
- LLMs673
- Machine Learning622
- Open Source568
- AI Agents564
- AI483
- Developer Experience448
Weekly digest
The best engineering reads, once a week.