Organizations face three recurring data problems—inconsistent metric definitions, fragmented access controls, and metric changes that don't propagate everywhere. A semantic layer solves this by centralizing metric definitions and governance in one place, so all tools pull the same numbers and changes cascade automatically. It won't fix bad data at the source, but it shrinks the surface area you need to manage and makes self-service analytics actually work.

• The same metric getting defined differently across Tableau, Power BI, and Python isn't a minor annoyance—it's a root cause of bad executive decisions.
• Hiring more BI analysts as gatekeepers just creates ticket queues and bottlenecks; it doesn't fix fragmented governance across tools.
• A semantic layer centralizes metric definitions and access controls so a single change (e.g., redefining ARR) propagates automatically everywhere instead of requiring manual updates across systems.
• Centralizing definitions and logic in one place also makes the data self-documenting, enabling real self-service instead of ticket-based requests.

The article argues that as AI automates data queries, pipelines, and models, the real value shifts to “measurement engineers” who decide if we’re measuring the right things and interpret ambiguous results. It breaks down why judgment—construct validity, reliable metrics, and decision theory—is a teachable skill that organizations must build into hiring, training, and structure.

• As AI automates SQL, pipelines, and modeling, the bottleneck shifts to judgment: deciding whether you're measuring the right thing.
• Teams that track hundreds of metrics tend to cherry-pick supporting ones instead of narrowing to a few that predict real outcomes.
• Rising internal model evals can coexist with falling user satisfaction because evals often measure fluency, not usefulness.
• Borderline A/B test results demand power analysis and decision theory, not just p-values, to judge if effects like a 1.5% retention drop are real.

The ninth AI Index report from Stanford HAI compiles global metrics on AI research, performance, adoption, economics, policy, and public opinion through 2025. It highlights rapid generative AI uptake, gaps in governance and evaluation, new economic and labor estimates, and standalone chapters on AI in science and medicine.

• Generative AI adoption hit ~53% of the population in just three years, faster than PCs or the internet, with corporate investment more than doubling in 2025 and 88% of organizations now using AI tools.
• Benchmarks are breaking down as labs disclose less, tests saturate, and independent evaluations sometimes contradict developer claims.
• 2025 saw diverging global AI policy: EU AI Act bans took effect, the US leaned deregulatory, Japan/South Korea/Italy passed new laws, and most new national AI strategies came from developing countries emphasizing "AI sovereignty."
• AI in science and medicine moved from isolated assistance to running full experimental workflows and system-wide hospital deployments (ambient scribes, diagnostic tools, FDA approvals).

Rill’s Metrics SQL lets you define business metrics once and query them using plain SQL across dashboards, notebooks, and AI agents. It compiles metric views into optimized OLAP queries, handling grouping, filters, time functions, and security automatically.

• Define a metric once in a YAML-backed metrics view and query it as plain SQL from dashboards, notebooks, and AI agents alike, instead of redefining it in dbt, Looker, Python, etc.
• A parser/compiler/executor pipeline rewrites simple queries like "SELECT country, revenue FROM revenue_metrics" into full OLAP SQL with correct GROUP BY, joins, and filters automatically.
• Security (row-level and column permissions) and SQL-injection-safe parameter binding are enforced consistently at the executor stage for every consumer.
• Works across multiple backends (ClickHouse, Snowflake, DuckDB, Druid) and can leverage existing database optimizations like materialized views and indexes for performance.

This article examines the high rate of unused and broken dashboards in organizations, highlighting how they often fail to provide lasting value. It discusses the disconnect between dashboard creation and actual usage, driven by shifting priorities and limited attention spans within teams. The piece also touches on the implications of this phenomenon for organizational behavior and project management.

• About half of an org's dashboards audited turned out to be broken or ignored, raising the question of why they were built at all.
• Dashboards act as "grave markers" for past priorities—built for a moment of attention that fades as new projects compete for focus.
• Letting teams self-manage their own dashboards helped somewhat, but didn't solve the core problem since attention still shifts away as new initiatives emerge.
• Organizational attention is a genuinely limited resource (with academic grounding), so strategic planning that overcommits people guarantees old dashboards get abandoned.

The article discusses the shifting landscape for data scientists and machine learning engineers in the age of large language models (LLMs). It emphasizes the importance of data science fundamentals in evaluating AI systems, addressing common pitfalls in metrics, experimental design, and data quality. The author argues that the core work of data scientists remains vital, even as their roles evolve.

• Off-the-shelf eval framework metrics often mislead teams; digging into your own data to find relevant metrics is what data scientists actually do.
• Using LLMs as judges without validating them against human labels is a common, risky shortcut.
• Synthetic test data that isn't grounded in real production logs leads to flawed experimental design and misleading results.
• Outsourcing labeling away from domain experts degrades data quality and undermines the whole evaluation process.