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
GPU Management: Why Idle GPUs Are the New Grounded Aircraft
Enterprise AI is shifting from a primary focus on model capability to the utilization of scarce, expensive GPU capacity. Like aircraft, GPUs accrue financing, depreciation, power, and cooling costs by calendar hour, while producing value only during useful compute hours; unlike aircraft, they cannot freely absorb workloads with different memory, latency, and duration profiles. The article explains how peak-sized clusters, mixed workloads such as training, fine-tuning, quantization, real-time and batch inference, embeddings, and evaluation can leave capacity stranded even when dashboards show high occupancy, and argues that API pricing can motivate enterprises to own infrastructure. It presents specialized models and GPU orchestration as complementary levers: specialization reduces each workload’s footprint, while management reallocates freed capacity across workloads and queues. The conclusion is that installed capacity alone does not determine returns; enterprises need both strategies to close the gap between GPUs owned and useful output.
How we set up our cloud agent environment
Setting up a cloud-agent environment for the Cursor monorepo required treating development infrastructure as a product for agent users. The team aligned cloud VMs with local development by adapting utilities and setup scripts for Ubuntu, adding dependencies to a Cursor-defined Dockerfile, and introducing security controls for secrets and network access. To make the repository easier to operate, it built anydev to start services, route utility scripts, explain subcommands, and supervise long-running builds. Cursor Cloud MCP and Cloud Doctor then inspect environments, distinguish transient from salient failures, perform root-cause analysis, open high-confidence fixes, and improve workflows using traces. The resulting end-to-end testing and recorded demos helped cloud agents grow from about one in ten merged PRs in December to more than half, with the post identifying tool parity, documented skills, and core-workflow verification as readiness checks.
How to use Google microbenchmarks for evaluating TPU performance
Evaluating TPU performance requires measurements beyond product specifications, because real-world behavior depends on architecture and workload constraints. The suite measures network collectives, compute, HBM bandwidth, host transfers, and Ragged-Paged Attention primitives, using metrics such as GB/s, latency, TFLOPs, MFU, and TTFT-related throughput. Its src and configs directories provide implementations and tunable parameters, while sample Kubernetes recipes connect measurements to TPU architecture and runtime behavior. Roofline analysis uses peak MXU throughput and HBM bandwidth to distinguish compute-, memory-, and network-bound workloads and guide kernel, sharding, or rematerialization choices. In a 110B MoE workload on a 4x4x4 TPU 7x configuration, microbenchmark-guided changes addressed ICI stalls and memory-bound attention, reducing training step time by 21.2%.
Meet Stripe's Knowledge AI Platform
Stripe built Kai, a knowledge AI platform for non-engineering work that existing no-code and coding agents could not support with Stripe’s required data security and workflow specificity. It serves tasks including account research, incident triage, revenue modeling, compliance reviews, and data-warehouse queries, while adapting to different tools, data sources, outputs, and definitions of completion. Kai is organized into surface-agnostic APIs, AgentStudio for domain teams to build and govern agents, and shared execution environments with per-session Kubernetes sandboxes, multi-tenant virtual filesystems, access controls, and long-session state management. The platform connects to more than 1,000 skills and tools and supports web, Slack, embedded, and custom application experiences. Within two weeks of its April launch, most of Stripe was using Kai; it now has 83% weekly active users, and reported effects include 25,000 annual hours shifted from administrative work and higher sales activity and deal creation among Account Executives.
Quality care is the mission. Finance protects the margin.
Healthcare finance teams must protect margins amid rising medical costs, denied or underpaid claims, complex payment arrangements, and cash trapped in receivables, while fragmented systems and delayed information increase decision risk. The post presents ontology as a way to preserve the business meaning behind figures, linking numbers to service lines, payers, contracts, and changing context rather than treating accuracy alone as correctness. Databricks Genie is described as a governed, data-smart AI coworker that answers finance questions with sourced figures, traces them to their origins, respects permissions, and keeps a person in the loop. It applies this model to care costs exceeding reimbursement, revenue lost to denials and underpayments, and aging or unbilled receivables, with the intended actions of renegotiating rates, preventing claim errors, accelerating collections, and protecting margin.
Manufacturing runs on capital. Finance protects the margin.
Manufacturing finance must protect margin by keeping capital moving through inventory, receivables, and plant equipment. The post argues that volatile supply chains, shifting demand, rising costs, and increasingly influential agents make that work faster and more complex, while an estimated $1.7T remains trapped in excess working capital across large US companies. It presents ontology as a way to preserve the meaning and context behind figures, including plants, SKUs, customer terms, and changing business conditions. Databricks Genie is described as a data-smart AI coworker whose ontology learns from business systems and questions, produces sourced and governed answers, and helps finance identify trapped inventory cash, aging receivables, and underperforming assets. It readies actions such as releasing inventory, accelerating collections, or redeploying capital, while a person remains responsible for the decision.
Energy runs on volatile markets. Finance protects the margin.
Energy finance must protect margin as hourly power and fuel prices, shifting forward curves, contract settlements, hedges, and major grid and generation investments make business conditions more complex. The post argues that accurate figures are not necessarily correct unless they retain context about the underlying asset, market, and contract, motivating a live ontology that keeps business meaning current. It presents Databricks Genie as a data-smart AI coworker that learns from enterprise systems and questions, returns sourced answers, preserves permissions, governs AI cost, and shows its work. The proposed uses cover live margin, revenue risk across PPAs and hedges, and funding AI-driven buildout, with a person making trading, dispatch, hedging, or capital decisions. Genie is described as helping finance identify risks early and prepare actions while keeping human owners accountable.
How agentic AI can help telecom finance teams protect the margin when every moment matters
Telecom finance teams face revenue leakage when services go unbilled or uncollected, fraud and partner-settlement errors drain charges, and customer churn removes future spending. The source argues that fragmented ordering, billing, ERP, and spreadsheet data makes month-end reconciliation too slow, turning discrepancies found weeks later into write-offs rather than recoverable revenue. It presents Databricks Genie as a data-smart AI coworker whose ontology captures business meaning across systems, stays current, and grounds sourced answers in governed data. Genie can answer billing, invoice, spend, and variance questions, surface anomalies, and support action while a person remains responsible for decisions; Lumen Technologies is cited as using it across the Office of the CFO. The text says Genie does not make billing, fraud, or pricing decisions.
Developers are attached to tools because tools encode trust
Traditional developer tools like Vim, Emacs, and IDEs earn trust through predictability, bounded roles, and muscle memory developed over time. In contrast, agentic coding tools operate across the entire software development lifecycle using ambiguous natural language, rapidly generating vast amounts of code that developers do not inherently trust. This influx shifts development bottlenecks from code authoring to code review, validation, and infrastructure cost management. Tooling additions such as automated code reviewers, context managers, and memory systems cannot repair broken software development lifecycles unless organizations actively adapt their culture and workflows. Teams can establish trust in agentic environments by providing explicit contextual specifications, reusing verified components to avoid duplicate implementations, and restricting non-deterministic artificial intelligence to appropriate problem domains.
Building an agentic harness that outlasts the model
Shopify’s Application Security team built an agentic harness that scans software for vulnerabilities, proves candidates with real tests, and opens Shopify-specific remediation pull requests. Its Dispatch orchestrator partitions repositories, runs category-specific Hunting agents in parallel, verifies findings sequentially with a different model, and persists architecture artifacts for later diff-based scans. Test oracles require realistic integration or functional coverage, including cross-tenant fixtures for IDOR checks, while unproven candidates are rejected or downgraded. Across more than 80 applications and thousands of scans, the workflow produced over 300 findings, including two rated Critical by Shopify’s severity calculator, with full scans costing $50–$300 and incremental scans $5–$50. The post concludes that durable value lies in the harness’s verification, partitioning, cross-model review, and deterministic infrastructure rather than in any single model.
The audience is the asset. Media finance teams need to understand them to protect the margin.
Media finance teams are tasked with understanding how audience value flows across subscriptions, advertising, and content investment so the business can protect margin. Streaming has turned one wholesale audience into multiple monetization strategies, while ad-supported tiers now account for 59% of new streaming sign-ups, making timely measurement and pricing analysis more important. Ontology preserves the meaning and context of figures as audiences, titles, channels, and business conditions change, distinguishing a correct answer from one that is merely accurate. Databricks Genie is described as a governed, data-smart AI coworker that answers sourced natural-language questions, learns from interactions, and shows its work; Genie-powered apps let hundreds of DIRECTV analysts and leaders query more than 1,200 customer-level attributes, while people retain decision authority.
Chief data officer: role, responsibilities, and career guide
The chief data officer (CDO) is a senior executive who treats enterprise data as a strategic asset, overseeing data strategy, management, quality, governance, and its use in analytics and AI. The role sits between business strategy, information technology, and data science, while distinguishing the CDO’s focus on data from the CIO’s responsibility for technology infrastructure. Responsibilities span the data lifecycle, governance frameworks, access controls, quality metrics, business intelligence, analytics prioritization, and organizational data capability. The role has shifted from compliance-focused stewardship toward enterprise AI strategy, with enablement-oriented governance making reliable, AI-ready data accessible while protecting its integrity. The guide also presents executive authority, data literacy, and leadership judgment as important conditions for delivering measurable business value.
Our position on open-weights models
Anthropic CEO Dario Amodei states that Anthropic has never advocated banning open-weights models, while distinguishing models without dangerous capabilities as a public good from risks associated with sufficiently capable systems. The post identifies two concerns: authoritarian governments gaining military superiority or enabling repression, and powerful models being misused for cyberattacks, biological attacks, or serious alignment problems. It argues open weights can increase misuse risk because guardrails and monitoring are difficult after release, but says banning their use by US businesses would not address bad actors. Instead, Amodei supports restricting powerful chips and chipmaking equipment exports to China, disrupting industrial-scale distillation, and requiring global pre-release safety testing for sufficiently capable open and closed models. He agrees open weights can expand access, competition, and customer control, but says claims about safeguards should be tested empirically.
How Vercel used Cursor to build Queues
Vercel built its durable event streaming system, Vercel Queues, entirely with Cursor, using agents across three rewrites and validating changes against real AWS environments. Engineers had agents work on the Queues API, connect to AWS, inspect DynamoDB and Kinesis side effects, inject faults, simulate bugs, and verify results, while Cursor retained context through long sessions and compaction events. The workflow also supported model switching, parallel planning agents, inline review, stacked PRs, and asynchronous Cloud Agents. Among Vercel’s Cursor power users, PR throughput increased 54%, PR cycle time decreased 89%, resources per feature fell 27%, and the company reports 104 hours saved per developer annually. Product managers also use Cursor for repository analysis, product analytics, and small fixes without drawing on engineering resources.
The EU Digital Product Passport: a traceability deadline
The EU’s Ecodesign for Sustainable Products Regulation (ESPR) will require in-scope products sold in the single market to carry a machine-readable Digital Product Passport (DPP), with batteries first from February 2027. The passport links a unique identifier and data carrier to lifecycle information that must remain accurate, while operators retain responsibility for data stored on their own backend, tiered access, supplier inputs, and any Registry registration. Implementation is primarily a data-integration and governance problem, spanning tier-N suppliers, per-unit operational records, lineage, analytics, AI, and controlled sharing rather than QR-code generation. Databricks components including Lakebase, Unity Catalog, Lakeflow Spark Declarative Pipelines, Databricks Apps, and OpenSharing are presented with a battery-focused Solution Accelerator as an operator-side reference architecture. The stated benefits extend beyond market access to faster recalls, sourcing-risk visibility, and lineage-based sustainability reporting, but technology alone does not establish compliance.
AI Sovereignty is Your Alpha: How to Avoid Transferring Your Alpha to a Hosted Model Provider
The document examines how use of third-party AI model services can expose an organization’s “alpha”—institutional knowledge and tradecraft embodied in data sent to and generated from models—to hosted model providers. It identifies risks involving provider reuse, storage, human review, model or service improvement, contractual liability caps, ZDR-ineligible beta services, safety-classifier triggers, and inference routed through prohibited regions. Its recommended approach combines contractual protections with operational controls: define robust Zero Data Retention, limit data use to service delivery, bind both hyperscalers and relevant AI labs, maintain an allow-list, block beta headers, and constrain unilateral term changes. It also calls for observability and contractual incident safeguards, including investigation periods, migration buffers, and regional routing limits, while noting that the document is not legal advice.
AI customer service: strategy, agents, and solutions guide
AI customer service combines natural language processing, machine learning, predictive analytics, generative AI, and automation to route requests, generate responses, and support resolution across channels. The guide distinguishes AI agents from scripted chatbots: agents reason over context, call external tools, and complete multi-step tasks such as checking shipping data and issuing a partial refund. It presents AI as a layer that absorbs routine volume while human agents retain judgment over complex or sensitive cases, citing potential gains including more than 70% query automation, up to 30% lower operating costs, and a 15% improvement in customer satisfaction. It recommends evaluating integration, decision transparency, production support, security, and compliance, then starting with one measurable, high-volume use case and expanding only after consistent resolution quality.
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.
Top topics
- Architecture830
- Performance812
- LLMs648
- Machine Learning617
- Open Source561
- AI Agents542
- AI454
- Developer Experience446
Weekly digest
The best engineering reads, once a week.