One of the most frustrating parts of using @metabase for serious dashboards is managing SQL query variables manually.
When you build dashboards with several SQL questions, you often reuse the same filters across multiple cards: company, date, customer, category, etc.
The problem is that every variable configuration still needs to be handled manually: field mapping, widget type, label, dropdown behavior, single/multiple values.
This becomes painful fast.
I opened a feature request suggesting a better way to bulk-manage query variables, possibly through reusable presets, dashboard-level schemas, or JSON import/export.
Discourse discussion: https://t.co/yBKQYl3dyk
GitHub issue:
https://t.co/5Chd0tEoPb
Manually debugged a data mismatch between a SaaS platform and a data warehouse through @metabase . With @OpenAI Codex, I could inspect the API responses directly, compare them against the DB state, and trace the issue back to the sync logic: we were upserting records but not replacing stale snapshots.
Human judgment + AI-assisted debugging = found the real bug, not just the symptom.
You donโt hire me.
You hire me + the โฌ100/month Codex monster in my terminal.
Data, strategy, content, security, marketing, distribution.
Everything goes through it now.
@nic_amadio Traffic is a big issue in Tessin. Minimising the use of car can drastically improve the quality of your life, but of course your family situation matters