#estimating
Live, measured metrics for the hashtag #estimating from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #estimating
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-28 23:54 UTC1 uses by 1 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-28 23:54 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 23:54 UTCEverything below is measured over the latest 40 public posts (spanning ~24336 hours).
Posting hours (UTC) — busiest: 00:00
Languages: English (38) · Polish (1)
Avg boosts / post: 2.7
Top of the latest posts
The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. — Tom Cargill #estimating
#scrum #scrumteam #scrummaster #scrummasters #scrummastercommunity #scrumhumor #StoryPoints #story_points #estimating #estimation #Meme #memes #Humor #humour
4/ I've been thinking about #uncertainty from risk POV, & Doug Hubbard's concepts of calibrated estimators. My team does weekly calibrations for #estimating uncertainty. Listening to Choi-Greene talk about AI's certainty - confidently wrong
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/estimating