How to Stop Dashboard Sprawl and Restore Trust in Your BI
How to Stop Dashboard Sprawl and Restore Trust in Your BI See why dashboard-driven design causes it and how a warehouse data model creates one source of truth. Key takeaways The cause: dashboard-driven design, where every stakeholder request becomes its own report with logic built fresh inside the BI tool.
Also shipped Nov 19, 2026Xebia in November 2026 →
Gemini 3.6 Flash will be retired on November 19, 2026
Databricks announced that Google Gemini 3.6 Flash will be retired on November 19, 2026, after which calls will automatically redirect to Gemini 3.8 Flash.
Wait for pull request events with GitHub CLI
GitHub CLI gh v2.105.0 added preview support for gh event listen, enabling users and agents to subscribe to pull request events without polling.
Gemini 3.6 Flash is retired
Google Gemini 3.6 Flash was retired on November 19, 2026, with API calls automatically redirecting to Gemini 3.8 Flash at the same price.
Gemini 4 Hydrogen in CodeMender (Preview)
Google Cloud added preview support for Gemini 4 Hydrogen in CodeMender, accessible by supplying the --model gemini-4-hydrogen flag to cm subcommands.
Data Engineering Agent observability is generally available in BigQuery
BigQuery added general availability for Data Engineering Agent observability, allowing users to track request volume, model latency, token usage, and tool traces in Cloud Monitoring and Cloud Trace.
BigQuery introduces AI indexes in Preview
Google Cloud released AI indexes in BigQuery in Preview, enabling natural language search across columns using the AI.SEARCH function without manual embedding generation.
More from XebiaEvery Xebia release →
AI Gateway Traces: How to Find and Fix Wasted Tokens in Your AI Agents
AI Gateway Traces: How to Find and Fix Wasted Tokens in Your AI Agents An AI gateway sits between your agent and the LLM provider. Every request and every response passes through it, so it can record the whole story of a task. The fastest way to cut what your AI agents cost is to read what they actually do. An AI gateway records every step an agent takes.
Stop Terraform toolchain drift with mise and Renovate: one pinned file per repository
Stop Terraform toolchain drift with mise and Renovate: one pinned file per repository How thirty Terraform module repositories moved to one pinned toolchain, with Renovate keeping the pins current and CI carrying the same ones At a client, the platform team I work in maintains about thirty reusable Terraform module repositories.
Knowledge Up, Context Down
Knowledge Up, Context Down A series on managing knowledge when working with AI. When I work with AI tools, the quality of the result depends less on the model and more on the context it gets: which decisions were made, why, and what applies to this project, this team and this organization.
Fast With AI, Lost Without Context
Fast With AI, Lost Without Context Part 1 of Knowledge Up, Context Down. Fast results with AI, then losing track of decisions. New to this series? Start with the overview . Next: part 2 . I recently built a proof of concept with AI tools. I had something running very fast.
Your Own Context and When to Share It
Your Own Context and When to Share It Part 2 of Knowledge Up, Context Down, about personal knowledge. Keeping your own context small, and sharing what’s useful. New to this series? Start with the overview . Previous: part 1 . Next: part 3 .
Record Decisions and Their Reasons as You Go
Record Decisions and Their Reasons as You Go Part 3 of Knowledge Up, Context Down, about project knowledge. Recording decisions and their reasons while you work. New to this series? Start with the overview . Previous: part 2 . Next: part 4 . The project level In Part 1 – Fast with AI I described a proof of concept where I lost track of decisions.
A Shared Way of Working That Everyone Can Check
A Shared Way of Working That Everyone Can Check Part 4 of Knowledge Up, Context Down, about team knowledge. Shared memory that people can inspect and correct. New to this series? Start with the overview . Previous: part 3 . Next: part 5 .
One Base Context for Every Team and Agent
One Base Context for Every Team and Agent Part 5 of Knowledge Up, Context Down, about organization-wide knowledge. The base context every person and agent starts from. New to this series? Start with the overview . Previous: part 4 . Next: part 6 . The organization level At this level I’ve run into two opposite problems. Too little information.