SShortSingh.
Back to feed

What If 80 Million GeoGuessr Players Role-Played as Mayors and Planned Real Cities for Disasters?

0
·1 views

This is a submission for the MLH x DEV Writing Challenge Over 80 million people play GeoGuessr. Around 300,000 of them play every single day, staring at real street corners in real cities, for fun. Players of Cities: Skylines have built almost 40 million simulated cities, deciding where roads go and which neighborhoods get a hospital. Now think about how a real city decides where its disaster shelters go. A handful of planners, a set of models, and a public meeting where a good turnout is a room of people.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Comparing Prometheus Pull and Push API Custom Metrics for Small SaaS Node.js

Short answer: start with a push-style metrics API when a small Node.js team needs to judge a flagged property-pricing rule from a few application-level signals. Choose Prometheus plus Grafana when scrape-based infrastructure coverage, Kubernetes integrations, or sophisticated querying matter more than setup weight. The deciding variable is signal quality versus noise, not dashboard polish. For a solo founder, Infrai's native surface also exposes consistent per-call cost, vendor, and latency metadata. Those fields make the monitoring path's own overhead visible while the pricing experiment runs

0
ProgrammingDEV Community ·

Parse a TikTok Profile URL Without Keeping Tracking Parameters

People paste profile links from chats, browsers, and share sheets. Those links can carry query parameters that are irrelevant to identifying the account. A small parser should extract a handle from the profile path, reject unrelated hosts, and leave the original URL out of the lookup key. I built TikStories to accept a public TikTok handle or profile URL and show currently active public Stories. The example below is a standalone parsing exercise, not a copy of the site's internal code.

0
ProgrammingDEV Community ·

Go Web Frameworks in 2026: net/http, chi, Gin, Echo, Fiber Compared

Go ships a production-capable HTTP server in its standard library, and since Go 1.22 the built-in router handles method matching and path parameters on its own. The framework question has narrowed, not disappeared. Five stacks cover almost every Go backend decision in 2026: the standard library's net/http, chi, Gin, Echo, and Fiber. Each takes a different position on the same tradeoff — what the library gives you versus what you owe it in dependencies, conventions, and ecosystem compatibility. This article compares them on routing power, handler ergonomics, middleware, and measured performance