thingsilearned
Many debates about AI are complicated and hard to resolve, but this one isn’t: all of these stories are clearly false. Some evidence:
The AI experts who aren’t affiliated with big companies are just as concerned as the ones who are.
The AI company leaders giving these warnings were giving the exact same warnings before they had AI companies - and in many cases, before they worked in the industry, or before the industry existed.
If these corporate plots were real, they would be incredibly dumb.
We already have variables and links (which work with variables)[1]. Variables create interactive menus that update urls, queries and charts. If you have a variable `region` and you set it the url will add a get param ?region=<value>
Each chart also has a basic `link:` property can use to link to the existing or other urls with the variables set. For example
type: bar x: revenue y: region link: '?region={{ region }}'
The result is a big range of flexibility, for example [2] here's an example of Conways Game of Life inside of dbt Charts.
[1] variables example - https://play.dbtcharts.com/?example=variables%2Fall-input-ty.... [2] Conways game of life - https://play.dbtcharts.com/?example=variables%2Fgame-of-life...
> dct validate <file.yml>
Or any of the other commands that read the file will quickly fail with any syntax or SQL issues. It’s not just an open schema.
Who knows, with AI this may be the future. Visualizations were created to help us understand data. Florence Nightingale published them "to affect thro' the Eyes what we fail to convey to the public through their word-proof ears."
Often a formula better represents a situation. But I'm not sure how much impact they'd have in spreading that understanding outside of a formula-minded audience.
The raw HTML/SVG or base libraries approach may well win out, but it does make it quite hard or impossible for humans to follow along and verify for instance where the numbers on a chart came from.
I think in a future where AI's doing all that verifying (or we just trust it), the AI might still prefer to use a DSL like ours because the abstraction maintains consistency, lowers maintenance, and saves a lot of tokens.
But the most helpful bits of a structured DSL are for sure still for humans. The structured format ensures things are readable and testable. Ours also enables a generative UI, which for now at least is still a much faster way to make visual edits while working with an AI, vs always through it.
When making dashboards with claude or other agents, a lot of free-form artifacts are created that makes it hard to audit and scale. dbt Charts is a simple YAML dialect that declares and renders a chart (think markdown but for dashboards). Along with dbt its Apache 2.0 and launched today.
We hope this language + AI help make the BI space more open with dashboards as concise auditable code. Would love any thoughts and feedback.
Fivetran and dbt are one company now
github: https://github.com/davefowler/markdown-svg playground: https://markdown-svg-production.up.railway.app
Show HN: A tagged template literal utility for clean LLM prompt generation
https://github.com/davefowler/llm-prompt-tag
Making prompts for llms with conditional context gets really messy. I've not seen a library that does this in a clean way and made a fairly elegant solution with template literals.
https://github.com/davefowler/prosemirror-suggestion-mode
and now I'm building it into my reading and note taking app for a better interaction of AI giving assisted edits, most similar to the Patchwork project from ink and switch https://www.inkandswitch.com/patchwork/notebook/07/
Show HN: After Intelligence – a prompt game for your future
One of the main points in the essay: "The problem with political correctness was not that it focused on marginalized groups, but the shallow, aggressive way in which it did so"
And your comment is a classic example of that behavior.