Organização
vibedasher · servido de eu-central-1
We build the host. These seven are our own work, published from our own account, and they are here as worked examples rather than as a portfolio — each one carries the dataset it reads, the SQL it runs and the thing about it that was hard.
Two years of Apple price data, published public. One query fetches a 33 KB Parquet extract; the window is closed, so the data stays as of 2017-02-16.
Two and a half centuries of fossil-fuel carbon in 5.8 KB, published public, one query over the credential-free lane.
Sixty-five years of population for every country: a choropleth encoding a rate, circles encoding a count. One query, a 102 KB extract, every tile re-derived when the year scrubber moves.
The one here that does NOT use the query lane. 9,994 order lines ship compiled into the bundle and every tile cross-filters every other. Its wasm extract exists and is never asked for.
SYNTHETIC — the event stream is generated, seed 20260904, and it is not usage data from vibedasher or any real product. Three queries over a 141 KB extract. It is here for the censoring rule; the numbers mean nothing.
The first dashboard here that is not frozen. A connection-backed Postgres dataset on a daily refresh that rebuilds its wasm extract. It reads as of 2026-09-30, the newest publication date in the rows, and that date moves on its own.
Two datasets behind one dashboard, both on a schedule: the long count series daily, the event window every three hours. It reads as of 2026-01-01 because the long series advances once a year; the event tile inside it is hours old.
Three datasets, and only two are fetched when the page opens. The story is told from 62 KB; the 2.1 MB name table that answers "what about my name?" is requested the first time a reader asks and never otherwise.
A cron reloads the source table from JPL at 05:40 UTC; the dataset refresh re-reads it at 06:25 and rebuilds the wasm extract. A newly discovered object brings its past approaches with it, so a reload can add a pass from 1911.