#SpecificationByExample
Live, measured metrics for the hashtag #SpecificationByExample from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #specificationbyexample
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 14:04 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 14:04 UTCNo related tags with measured usage found for #specificationbyexample.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 14:04 UTCEverything below is measured over the latest 4 public posts (spanning ~26647 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 0.3
Top of the latest posts
Check out our blog. We write about #EventSourcing #CQRS #DomainModeling #SpecificationByExample #FunctionalProgramming https://fraktalio.com/blog/
The Decision-making process (a #Decider) is driven by data in which you make new decisions (events) based on the current state (current events) and action (command) being triggered. https://fraktalio.com/blog/specification-by-example.html #
@thirstybear My reading of #SpecificationByExample was that it was simply an approach to the acceptance testing part of #BDD, not that it was 'inverting the pyramid' nor seeking to replace unit or integration tests.
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/specificationbyexample