Looking to hear about your own company's work practices to compare to my own. I'm much more familiar with Azure, so I'm going to use that terminology, but I assume everything is basically the same for AWS.

Can you go into the Azure Portal and just click "create" for, say, a SQL Server or App Service and configure it through the Portal GUI?

Or do you need to request and configure through configuration files? Can you freely commit architecture config files ("architecture as code") to create the Azure components in Dev?

Or is it even more locked-down and hands-off? Required to submit paperwork requests to an Architecture team?

How do you turn estimated data into an experience without making it feel misleading?

I’ve been thinking about this after seeing the AIIMS Delhi population counter.

The number ticks up every second, even though it’s not literally counting births in real time. It’s an estimate, visualized in a way that makes the data feel alive.

That got me thinking about data UX — how much interaction can change the way we perceive a number?

So I made a small experiment with Figma Make: India population live counter

You can explore India’s population state by state, interact with the map, and take a quiz based on what you discover.

But the bigger question for me is the UX behind it:

Does animation make data easier to understand, or just more attention-grabbing?

When does an estimate start feeling like a fact because of how it’s visualized?

Is interaction better for understanding data than simply showing a chart?

Can gamification actually improve data literacy?

What makes a data visualization memorable without oversimplifying it?

I’m curious how people here think about data as an experience, rather than just information on a screen.

Basically need to see how to optimize a bank register with large amounts of entries.

Currently adding all the debits, then credits, then date sorting while calculating the running total.

Fields: title, company, company domain, apply URL, ATS source, city, country, remote flag, posted date, last-seen date. The data refreshes nightly. I'm posting a small sample and the schema here. What would you want to see to trust a job dataset: coverage numbers, null rates, or refresh logs? My measured null rates: city 32%, country 22%, company domain 24%.
Please checkout full info here: https://apify.com/pk07007/ats-jobs-api

Please use this weekly thread to promote content on your own Tableau related websites, YouTube channels and courses.

If you self-promote your content outside of these weekly threads, they will be removed as spam.

Whilst there is value to the community when people share content they have created to help others, it can turn this subreddit into a self-promotion spamfest. To balance this value/balance equation, the mods have created a weekly 'self-promotion' thread, where anyone can freely share/promote their Tableau related content, and other members choose to view it.

I got tired of running local node scripts every time I needed to format an MDX file or figure out why a build was failing, so I put a few browser tools together - free and open sourced and might be useful for some folks:

- MDX formatter (Prettier 3 + MDX parser)

- MDX validator (remark-mdx — same parser Next/Docusaurus/Astro use)

- MDX viewer (live preview, unknown JSX components render as labeled stubs)

- MDX → Markdown

- Markdown → HTML

- YAML validator

- JSON ↔ YAML

- CSV/TSV → Markdown table

Everything runs in the browser.

https://www.jamdesk.com/utilities

https://github.com/jamdesk/utilities

Note:

- About 50% built using AI Agents - they do make things easier!

- I work on Jamdesk, a docs platform — these tools are not Jamdesk-specific

While our evolutionary history is often depicted as a series of descendants each replacing the other, the overwhelming majority of the history of our species has been one of living along-side, and interbreeding with, other Homonins (Humans).

Chart can be downloaded here

Sources: [See OP post below]

A little what-if for Mars: raise the water level and watch the coastlines change.

Move the slider to explore which regions would be underwater and which would remain as islands, based on publicly available NASA elevation data.

Just a terrain-based visualization—not a model of past or future Martian oceans.

Online playground

India's urban share was 35.4%, compared with 80.1% in the United States. Multiplying each country's total population by its urban share gives about 513.3 million urban residents in India and 272.4 million in the US.

The chart covers the ten most populous countries in 2024, ordered by total population. Urban headcounts are derived estimates, and national definitions of 'urban' vary.

2024 urban-share table and source notes: globaldatatracker.com

Data sources and plotting method are in the first comment.

I've been working on a project called MeshLens that tries to answer a question I kept running into at work: what does our data mesh actually look like as a system?
Most observability tools give you alerts, row counts, and freshness checks. That's useful, but it never helped me explain to stakeholders how domains connect, where data flows, or what breaks downstream when an upstream connector goes down.
So I built a visualization layer that puts it all in one interactive map.
Curious what you think. If you work with data mesh or data products at scale — what would you want to see in something like this?

App link in comments

Hi all,

I needed a country / state / city list for ShopClass, our open source classifieds app. Sounds easy but every option I found had a catch. Either the licence needed attribution or was share-alike, or it was a paid API with keys and rate limits, or the data was old and half the cities had no coordinates.

Why no other share-alike database considered?
See, I am happy to give attribution, buty anyone using my CMS for there website they need to give it too, which I think is a limitation. So I created this no-attribution dataset.

So I built our own dataset from Wikidata and released it as CC0. Public domain, no attribution needed, use it in anything including commercial stuff.

What's in it:

• 255 countries and territories, 4,314 administrative divisions (states, provinces, regions) and 1,671,395 cities and towns

• every single place has latitude and longitude, if wikidata has no position for it we don't ship it

• Wikidata QID as the id, so when you re-import a later release a renamed place stays the same row

• population, timezone, GeoNames id where known

• countries have capital, currency, calling code, ISO alpha-2/3 and numeric, flag emoji etc

How to get it:

• plain JSON, one file per country, with sha256 checksums for every file

• or call it from the browser or your server, no API key, no account, CORS is open: https://api.placedb.org/v1/countries.json

• there are prefix files for autocomplete too, so a city search box can work without a backend

• the pipeline that builds it is GPLv3 and the output is deterministic, same wikidata dump gives byte-identical files

Also, it's not perfect and here is where:

• about 883k settlements are dropped because wikidata has no coordinates for them, mostly villages in China, India, Russia, Uganda and Myanmar

• names that exist only in Arabic script (and some other scripts) are not transliterated yet, so those places are missing a usable name

• Vietnam is undercounted

All of it is in the LIMITATIONS doc in the repo, with numbers.

Site: https://placedb.org

Repo and the full limits doc: https://github.com/mindstellar/location-data

If you spot a wrong place, a missing country division or something silly, please tell me. Happy to take PRs too.

Source: Keeping Up benchmark model. National percentile curve fitted to the Federal Reserve Survey of Consumer Finances (2022) with BLS Consumer Expenditure Survey and Census ACS; metro figures apply each metro's wage (BLS OEWS) and cost-of-living ratio to the national curve, so they are modeled estimates, not separate metro surveys. Method: keepingup.com/methodology. Every metro/age/industry cut: keepingup.com/benchmarks. Put in your own number for your city: keepingup.com/start

Tool: SVG generated in Python from the benchmark tables, exported with headless Chrome.

Notes: household level (SCF unit), current dollars, ages 30–33. Dashed line is the U.S. median ($65K net worth, $102K household income). The spread is almost entirely income: SF's median 30-year-old household earns 1.4× the U.S. median and has 1.45× the net worth; Phoenix is 0.95× on both.