#TacticalDDD
Live, measured metrics for the hashtag #TacticalDDD from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tacticalddd
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 09:43 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 09:43 UTCNo related tags with measured usage found for #tacticalddd.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:43 UTCEverything below is measured over the latest 4 public posts (spanning ~41709 hours).
Posting hours (UTC)
Languages: English (3) · French (1)
Avg boosts / post: 0
Top of the latest posts
So how do we assess whether the code AI produces actually reflects the model we need? That is hard enough for people. How does an AI know when the model is shallow? #DomainDrivenDesign #SoftwareArchitecture #AI #TacticalDDD #CollaborativeSo
We started day 2 of the Tactical DDD training this morning, not with coding, but with discovering and formalising acceptance criteria through Example Mapping. These acceptance criteria then become input for domain modelling with responsibil
The coloured blocks on the flipchart make it click for most people. Once you can see where coupling creeps in and where boundaries should be, the conversations about architecture become much more productive. Tomorrow, we go into one of the
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/tacticalddd