#codingweek
Live, measured metrics for the hashtag #codingweek from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #codingweek
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-29 00:57 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-29 00:57 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 00:57 UTCEverything below is measured over the latest 5 public posts (spanning ~98 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.2
Top of the latest posts
#CodingWeek #progress This week, I've made significant progress, completing about 80% of the second email for my Short Ruby Email Courses. This email is about into the syntax of the endless method. My focus was on providing practical insigh
It is the middle of the week so maybe now it is a good time to take a small break and reflect on what you could NOT implement. Not everything you think should be implemented is essential now. Some things can be omitted or delegated for late
I was just doing some benchmarking of a bit of ruby code, comparing `value.digits(32)` to an explicit while loop that does the same thing, and decided to try it with `--yjit` too. * Normal ruby -- native method was more performant, although
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/codingweek