#codinghorror
Live, measured metrics for the hashtag #codinghorror from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #codinghorror
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 13:27 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 13:27 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:27 UTCEverything below is measured over the latest 13 public posts (spanning ~43419 hours).
Posting hours (UTC) — busiest: 12:00
Languages: English (12) · French (1)
Avg boosts / post: 0.6
Top of the latest posts
This is a real screenshot of actual production code. It ran for years and helped putting lots of food on the table. #refactoring #programming #imperative #codinghorror
Prolog Coding Horror https://www.metalevel.at/prolog/horror #HackerNews #Prolog #Coding #Horror #CodingHorror #PrologProgramming #SoftwareDevelopment #TechHumor
🎉 Oh, the horror! #GitHub decided that what developers really need is more popups! 🚨 Because clearly, the best way to streamline coding is to introduce surprise windows at every click. 🤦♂️ https://github.com/orgs/community/discussions/1
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/codinghorror