Replying to @data_purify
The pipeline overwrites automatically and doesn't keep the old values. Holding changes for review would stop the pipeline repairing itself.
1
12
The charts update themselves too: after every load the pipeline publishes small CSVs that Datawrapper reads.
Next: how it's built, and what the data shows.
Write-up, code and live charts: dev.to/initysl/building-a-se…
10
Rule 1: running it twice must change nothing.
Every load is an upsert on (city, date), so retries, overlaps and backfills can never create duplicate rows.
Rule 2: it repairs itself.
Each run re-fetches the last 7 days, so if a run fails, the next good one fills the gap. No manual fixes.
2
13
Replying to @AdewaleHamdalat
So, how are you enjoying Linux? What would you rate your experience? 😀
1
2
22
Replying to @hackSultan
Finalize and optimize a weather data pipeline for peak performance.
github.com/initysl/weather-p…
1
42



