You can’t unit test for taste
The article discusses the development of an app called In the Long Run, which allows runners to do virtual runs on famous routes around the world. The app's creator wanted to enrich the maps with interesting sights and historical sites, but found it challenging to scale this feature to routes in unfamiliar countries. The creator used a data source called GeoNames and built a pipeline to process the data and provide relevant points of interest to users.
- ▪The app In the Long Run allows runners to do virtual runs on famous routes around the world and tracks their progress on interactive maps.
- ▪The creator used GeoNames as a data source for points of interest and built a pipeline to process the data using Python, Apache Parquet, and DuckDB.
- ▪The pipeline included filtering and selecting specific feature codes, as well as using Wikipedia links as a notoriety and relevance signal.
Sidebar.io files mainly under design. We currently carry 33 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Karl Tryggvason - Developer Blog |
| Canonical URL | https://dev.karltryggvason.com/you-cant-unit-test-for-taste/ |
| Publication time | Tue, 30 Jun 2026 07:39:57 GMT |
| Retrieval time | 2026-06-30T07:54:24.163Z |
| Last seen | 2026-06-30T07:54:24.163Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | _qwUlSOeLsvQ |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
You can't unit test for taste 22 June 2026·12 mins I’m building In the Long Run where runners do virtual runs on famous routes around the world. The app tallies up your Strava mileage and plots your total distance as progress against country- or continent-spanning routes. The intention is to provide long-term inspiration and motivation; life is a marathon, not a sprint. You can have a bad month or season but still make progress on your virtual traversal of the world. The app shows your progress on interactive maps, which lets users do some exploring of their own. But I had long wanted to enrich the maps with interesting sights or historical sites. For routes I was familiar with I could build such lists myself but that doesn’t scale to routes spanning countries I am not familiar with.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Karl Tryggvason - Developer Blog.
Discussion
0 commentsMore from Karl Tryggvason - Developer Blog
