dbt Charts introduces an open-source, declarative approach that treats dashboards as code—living alongside dbt models so they can be version-controlled, reviewed in pull requests, and validated just like data transformations. By combining #SQL and YAML, humans and AI agents can collaboratively build, modify, and ship trustworthy visualizations that stay in sync when underlying models change. This gives AI the governed context it needs to produce reliable answers while extending analytics engineering practices all the way through the BI layer.

Sample chart definition using #SQL and YAML:


queries:
  revenue_by_month:
    #sql: |
      SELECT date_trunc('month', ordered_at) AS month,
             sum(product_price) AS revenue
      FROM MY_DATABASE.MY_SCHEMA.order_items
      GROUP BY 1
      ORDER BY 1

charts:
  revenue_trend:
    type: line
    query: revenue_by_month
    x: month
    y: revenue
    title: "Revenue by month"
https://www.getdbt.com/resources/webinars/introducing-dbt-charts-dashboards-as-code

Open Graph Image
www.getdbt.com

Introducing dbt Charts: Dashboards as code | dbt Labs

See how dbt Charts brings dashboards as code to your workflow, giving humans and AI governed context to build, review, and ship trusted dashboards.

LLM-generated TypeQL queries reach higher final accuracy than #SQL or Cypher once retries are permitted, because TypeDB’s strong type system converts most mistakes into clear, visible errors the model can fix, whereas #SQL failures frequently return silent wrong answers that go undetected. On the Reactome pathway database, TypeQL accuracy climbed from 75 % to 92 % with a modest retry budget while MySQL moved only from 82 % to 83 %, leaving TypeQL the most reliable choice for agentic systems that rely on error feedback.

https://typedb.com/blog/why-llm-written-typeql-can-end-up-more-accurate-than-sql-once-you-allow-retries

Open Graph Image
typedb.com

Why LLM-written TypeQL can end up more accurate than SQL once you allow retries

Comparing LLM failure modes across MySQL, Neo4j and TypeDB on the Reactome pathway database, and why retries make TypeDB queries so much more accurate.

Despite fears that AI would automate entry-level coding and trigger mass joblessness, data for summer 2026 shows recent college graduates overall weren't significantly worse off finding work than in recent summers, even when including those who want a job but aren't actively searching.

At the same time, hiring has slowed in highly AI-exposed occupations like programming, where computer science graduates are taking longer to land first roles and more often starting in lower-paying industries, reflecting not just AI but also trade policy, rates, and broader uncertainty, and pushing engineering work toward directing, evaluating, and improving AI output with stronger emphasis on domain knowledge, creativity, communication and leadership i.e. Ontology Economy

https://funginstitute.berkeley.edu/news/computer-science-after-ai/

Open Graph Image
funginstitute.berkeley.edu

Computer Science After AI - Fung Institute for Engineering Leadership

As AI reshapes computer science, creativity and effective communication are becoming increasingly essential to the industry’s future.

← Newer Page 1 of 19 Older →