Loading…
Browse by type
Explainer reads
Explainer posts on Yomu, summarised newest first.
- 1,316 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 Explainable AI (XAI)?
Explainable AI (XAI) comprises techniques that help people understand how AI systems produce specific outputs, particularly when machine-learning and deep-learning models operate as black boxes. It distinguishes intrinsically interpretable models, such as decision trees and linear or logistic regression, from post-hoc methods including SHAP, LIME, counterfactuals, saliency maps and Grad-CAM. A typical workflow selects a model and prediction, applies a method suited to the model and audience, reviews outputs such as feature scores or heatmaps, and uses them to assess accuracy, fairness, reliability and compliance. The article stresses that post-hoc explanations are approximations rather than definitive proof, so teams should validate them with domain expertise and, where appropriate, combine methods; MLflow and Unity Catalog can preserve explanation artifacts, lineage and auditability.
Enabling Evolutionary Database Development: database branching with Lakebase, continued
This installment revisits Evolutionary Database Design and argues that Databricks Lakebase removes the infrastructure constraints that kept several of its database-change practices aspirational. Lakebase is a managed Postgres database with compute separated from shared durable storage, while copy-on-write branches create a new pointer and divergence marker in roughly one second without copying parent data. That enables per-developer, per-PR, and per-experiment databases, real Postgres test branches instead of mocks or in-memory substitutes, and CI isolation at pull-request granularity. The updated playbook adds idempotent migrations, destructive testing, and database-level A/B prototyping, with Unity Catalog governance inherited by branches and agents receiving branches rather than production access. Jen’s example corrupts production-shaped data to test an inventory-code migration and compares column and lookup-table designs, rejecting the latter because its common read path requires a join.
Errors, traces, logs, metrics: when to reach for what
Modern application telemetry relies on four overlapping signals: errors, traces, logs, and metrics. Each telemetry type addresses distinct engineering questions and powers specific debugging workflows. Errors track grouped, actionable application crashes, whereas traces map timing and execution paths across dependency waterfalls. Metrics aggregate numerical measurements across historical deployments, and logs preserve complete state and decision-making context at specific moments in execution. Emitting telemetry directly into the format needed for a given workflow proves superior to relying on a single wide event, as tools like AI coding agents require structured spans to optimize execution paths while human debuggers rely on unsampled logs and metrics to pinpoint silent failures.
The AI and Data Transformation Playbook for Enterprise Teams
The playbook presents AI and data transformation as an enterprise capability built on trustworthy, well-governed data, rather than a model-only project. It explains how governance, scalable pipelines, and continuous quality monitoring address incompatible formats, missing values, duplicate records, and schema inconsistencies from systems such as CRM platforms, operational databases, IoT sensors, and cloud applications. Operational guidance covers KPI design, named pipeline ownership, review checkpoints, data mapping and lineage, automated de-duplication, deterministic enrichment, regulatory classification, and role-based access. It states that deterministic tests and human review remain necessary for AI-assisted code, while telemetry and quarterly audits help detect reliability, governance, and data quality degradation. The concluding position is that operational discipline—not model sophistication—supports reliable machine learning, predictive analytics, and generative AI outcomes.
What is AI Search?
AI search interprets natural-language questions using semantic understanding and large language models, then returns synthesized answers grounded in cited sources. Unlike traditional search, which matches query words to indexed pages, it tracks context and intent for conversational follow-ups. Its pipeline includes query understanding, embeddings, vector search, retrieval, LLM synthesis, and citations; retrieval-augmented generation (RAG) connects generated responses to source material. The article distinguishes consumer tools that search the open web from enterprise systems that retrieve private, governed company data while respecting access permissions. It concludes that AI search can improve direct information access but should not be treated as definitive, and that sensitive business use requires purpose-built platforms with governance, security, and retrieval quality.
What to look for when selecting a real-time analytical database
Real-time analytical databases must serve low-latency queries over data that is continuously inserted at high volume, rather than merely query a static dataset quickly. The article frames time-to-insight as the combination of time to ingest, time to transform and prepare data, and time to query it. It argues that batch-oriented ingestion, delayed visibility, scheduled materialized-view refreshes, and cache invalidation during writes can make production latency far worse than headline benchmarks. It recommends evaluating freshness under concurrent ingest and queries, whether one engine supports structured analytics, text search, vector similarity, and JSON, and whether index maintenance can avoid blocking ingestion. As an example, Bullet reportedly moved to ClickHouse Cloud, reducing data latency by 99.4% to under five seconds, achieving millisecond queries, and handling 1,000× more data at comparable cost.
Massachusetts Drivers: Proposed Regulations May Impact Your Ability to Earn
Massachusetts’s Department of Public Utilities (DPU) is considering proposed changes to transportation-network-company regulations that could affect drivers’ platform access, earnings, and operating costs. The proposal would expand the existing two-part background-check process by requiring seven years of driver-license history, birthplace, full Social Security documentation, Driver Verification System enrollment, and possible consultation with other agencies. It would also give DPU broader suspension authority, restrict hearing and deactivation-appeal rights, impose annual training, block vehicles with any open recall, regulate surge, and require rental vehicles to be electric within one year. Uber Black drivers could face new insurance, registration, and inspection requirements, while TNCs could incur fees that may increase fares. The post provides June 8, 2026 public-hearing details and instructions for submitting testimony.
Direct Preference Optimization Beyond Chatbots
DharmaOCR applies Direct Preference Optimization (DPO) beyond chat alignment to reduce text degeneration in structured OCR, where outputs are either acceptable transcriptions or failure loops. In a benchmark of Brazilian Portuguese structured-document OCR, vanilla degeneration rates among open-source model families ranged from below 1% to above 33%, while supervised fine-tuning (SFT) did not consistently reach production-acceptable levels. After SFT, the pipeline generated multiple candidates for 23,726 documents, used an automated LLM judge to score them, and retained the model’s degenerate outputs as rejected examples paired with chosen outputs. DPO reduced degeneration in every tested family, by 59.4% on average and up to 87.6%, without reducing extraction quality according to the benchmark; applicability is presented as dependent on failures being categorically identifiable, reliably scoreable, and sufficiently numerous.
Scaling Enterprise Conversational Intelligence: Cross-industry Technology and Functional Solutions Powered by Databricks Genie
Databricks Genie is presented as a cross-industry technology layer for enterprise challenges including financial planning, legal compliance, and IT operations. As a “Research Agent,” it can generate multi-step research plans to explain business anomalies and support answers with verifiable proof from the lakehouse. The post showcases partner solutions across technology, sales, marketing, HR, finance and procurement, supply chain, customer service, and IT operations, with examples spanning governed analytics, multi-agent orchestration, data observability, causal analysis, and incident management. These implementations aim to replace fragmented or static workflows with real-time, contextualized intelligence and production-grade agentic workflows, supporting anomaly investigation, root-cause analysis, ticket classification, and conversational troubleshooting. The stated goal is faster, more confident decision making across departments through governed self-service access to insights.
How ClickHouse became fast at joins
Over two years, ClickHouse focused on making joins faster for analytical SQL workloads, moving them from a performance gap to a first-class strength. The first year established the foundation with parallel hash joins, local automatic join reordering, filter pushdown, and execution improvements, producing a 4.4× speedup on the TPC-H SF100 join-heavy workload by version 25.4, compared with 22.4. The second year made optimizations effective by default, adding correlated-subquery support, lazy column replication, runtime filters, and statistics-based join reordering. Correlated queries can now run directly, while compact representations avoid copying repeated values and runtime filtering skips rows before hash-table lookups. Across the same benchmark and hardware, these changes delivered another 6× speedup, for a total 26× improvement; one six-table query fell from 3903.7 seconds to 2.7 while peak memory dropped from 99.1 GiB to 3.9 GiB.
Agentic BI: A Practical Guide for BI Teams and Business Users
Agentic BI uses autonomous AI agents to automate work between raw business data and actionable insight, including data preparation, query execution, chart and narrative generation, and report distribution. Traditional BI depends on analysts to gather data, write queries, maintain dashboards, and assemble reports, while agentic systems let business users ask natural-language questions and receive governed answers. The guide identifies a governed semantic layer as foundational, because shared metric definitions and deterministic execution help keep outputs consistent, auditable, and trustworthy, with human approval checkpoints for higher-risk handoffs. It recommends inventorying data structure, schema drift risk, and integration costs, then piloting a narrowly defined workflow and measuring time to insight, analyst hours reclaimed, satisfaction, and accuracy before expansion.
Data Science vs Data Analytics: Compare Careers, Skills, and Degrees
Data analytics and data science are compared as data-focused career paths, with analytics interpreting existing, usually structured data for trends and business decisions, while science builds models and automated systems to predict future outcomes. The guide contrasts typical questions, outputs, tools, education paths, and roles: analysts use SQL, Excel, Tableau, or Power BI for dashboards and reports, whereas data scientists use Python, R, Apache Spark, and MLflow for predictive models and algorithms. It describes analytics types from descriptive through prescriptive, and a data science workflow spanning collection, feature engineering, training, validation, and deployment, including unstructured data such as text, images, and sensor streams. It also explains collaboration, including analysts defining problems and baselines before scientists build models, and offers portfolio suggestions and questions for choosing a path.
Practical Data Lakehouse Examples and Use Cases
The article presents practical data lakehouse patterns for streaming analytics, IoT pipelines, machine learning workflows, and enterprise reporting, addressing the gap between theoretical definitions and deployable examples. It explains how a lakehouse combines low-cost, schema-flexible object storage with schema enforcement, ACID transactions, data versioning, lineage tracking, and query performance, allowing SQL and ML workloads to use shared open-format tables. Examples include second-level fraud detection, medallion-based historical analytics, predictive maintenance from sensor data, and governed customer 360 profiles. The implementation guidance covers raw storage and partitioning, centralized catalogs, decoupled compute, role-based access, time travel, migration coexistence, SLAs, observability, and lifecycle policies. Together, these patterns are presented as a unified architecture that reduces duplication and data movement while supporting governed analytics at scale.
Data Governance Architecture: A Complete Blueprint for Modern Organizations
Data governance architecture is presented as a blueprint for aligning policies, roles, processes, and technologies with business outcomes. It defines objectives including consistent data definitions, data integrity, layered access controls, and secure self-service analytics, while assigning responsibilities across executives, architects, engineers, analysts, managers, and compliance teams. Core principles are accountability, transparency, consistency, and stewardship, supported by federated ownership through councils, data owners, and embedded stewards. The discussion compares DAMA-DMBOK, TOGAF, and Zachman according to organizational scale, regulatory context, and architecture maturity, and describes modern patterns including lakehouse, data mesh, and data fabric. It concludes that effective programs require executive sponsorship, documented roles, measurable quality controls, iterative implementation, and sustained change management.
AI Governance Maturity Model: Matrix, Assessment, and Roadmap
The AI governance maturity model assesses how deeply governance practices are embedded across an organization’s data, process, and people dimensions, using five stages from Ad Hoc to Optimized. It frames the model as a diagnostic and roadmap for boards and executive sponsors, while a five-dimension matrix separately scores strategy and leadership, policy and ethics, risk management, data governance, and monitoring and observability. The progression moves from discovery and basic ownership through standardized controls, quantified risk, real-time indicators, lineage tracking, and automated, context-aware enforcement. The recommended roadmap starts with a baseline within 30 days, targets Level 3 across the five dimensions within 12 months, runs a 90-day pilot on two or three high-priority systems, then scales effective controls through CI/CD integration and monitoring, with quarterly reviews and annual reassessment.
What we’ve learned building cloud agents
Cloud agents have evolved from local-agent extensions into systems running on dedicated virtual machines, with isolated environments, dependencies, network access, parallel execution, and unattended long-running work. That shift makes the development environment a product: reliable execution increasingly depends on rebuilding tools, VM hibernation and resumption, image checkpointing and forking, integrations, and controlled access to secrets and networks. After a fragile work-stealing design produced roughly one 9 of reliability, the team migrated the agent loop to Temporal, whose retries and scheduling across failures helped exceed two 9s; Temporal now handles more than 50 million actions daily across over 7 million workflows. Decoupling agent-loop, machine, and conversation state enables independent pod lifecycles, asynchronous subagents, and retry-aware streaming, while shorter workflows simplify upgrades. The next goal is self-healing environments that can report and resolve missing secrets, blocked network access, or other obstacles.
RAG vs Fine Tuning: Enterprise Decisions for AI Models and AI Systems
The guide frames enterprise choice between retrieval-augmented generation (RAG) and fine tuning as a trade-off between injecting knowledge at inference time and changing model weights before deployment. RAG connects an LLM to external stores by embedding a query, searching vector databases for similar chunks, and adding retrieved context to the prompt, making current information and citations possible. Fine tuning uses curated input-output examples and supervised training to update parameters; full-model training is expensive, while LoRA trains a smaller set of added weights and can support a single-GPU pilot. The decision depends on whether the priority is stable behavior and output format or fresh, traceable knowledge, alongside data quality, latency, compute, and maintenance requirements. For many mature deployments, the guide recommends combining both: fine tuning for domain understanding and consistency, and RAG for real-time data.
Debunking 8 data layout myths: why Liquid Clustering outperforms partitioning
Partitioning has long been the standard physical layout for Hadoop- and Hive-era processing, but the post argues that changing Lakehouse workloads make fixed choices brittle. Liquid Clustering treats keys as guidance for file organization, allowing layouts to evolve, supporting low- and high-cardinality filters, maintaining file sizes, and enabling row-level concurrency. Using transaction-log metadata and per-column statistics, the post says modern Delta and Iceberg engines prune files rather than directories, and reports 35% lower clustering time, 22% faster queries, roughly 90% faster metadata-only deletes, and 23-minute planning for a 10-PB table. Conversion examples include Bolt’s 138% higher write throughput and up to 63% faster reads, while a 1.1-PB workload saw 5.9x faster queries, 86% fewer bytes read, and a 27% smaller table after clustering by date, hour, source, and id.
Beyond LLMs: Why Scalable Enterprise AI Adoption Depends on Agent Logic
Enterprise workflows are dynamic, long-running, API- and data-rich, and constrained by policies or regulations, creating challenges that an LLM alone may not handle efficiently. The article defines agent logic as software primitives—including knowledge graphs, algorithms, and program-analysis libraries—within an agent harness that steer models toward relevant workflow context. Examples span legacy COBOL and PL/1 understanding, automated test generation, incident investigation and code remediation, and compliance modernization; reported results include ~30× lower token consumption for application understanding, 20–45% higher test coverage, and up to 4.0× better incident-investigation performance than a ReAct baseline. A Condition Insights example reports 57% fewer unsupported claims and 77% lower average token usage, supporting the conclusion that structured guidance can improve quality, cost, and rule adherence.
Scaling up your microservice testing with Apache Spark
Microservices whose behavior depends on long-tail production inputs—such as payment cost estimation—are difficult to validate with unit and integration tests alone. The described pattern separates deterministic service logic from transport and side effects, then invokes that logic in Apache Spark across historical records enriched with the required dependency state. The resulting datasets can compare current and candidate implementations, quantify changed outputs, model future rule changes, and identify affected transaction or merchant segments. Replay inputs and artifacts are minimized and protected through tokenized identifiers, redaction, access controls, and retention policies, while smaller privacy-safe golden datasets run in pull-request CI. The approach complements, rather than replaces, unit and integration tests: golden datasets cover known service behavior, and full replays expose changes across the real production distribution before deployment.
Top topics
- Architecture830
- Performance812
- LLMs648
- Machine Learning617
- Open Source561
- AI Agents540
- AI454
- Developer Experience446
Weekly digest
The best engineering reads, once a week.