Back to @ThePracticalDev's profile

DEV Community engagement report

@ThePracticalDev - 317K followers on X

Measured over 70 original posts from a 30-day window, last computed on September 17, 2026.

Engagement

Bottom quarter for its size
Per follower
0.003%
of 317K followers
Per impression
0.147%
6.8K views on a typical post
Reach
2.15%
of its followers see a post
Typical post
10
interactions (median)
Saved
0.044%
3 bookmarks on a typical post
Posting rate
2.53/day
active 73% of days
Peak time
04:00 UTC
Friday

A typical post picks up 10 interactions against 317K followers, an engagement rate of 0.003%. Measured over 70 original posts, its engagement rate beats 14% of 15,519 tracked accounts of a similar size. That is a reason to look at how the audience behaves - reply depth, saves, whether the followers are recent - rather than a conclusion about it on its own. Posts are seen about 6.8K times each, and 0.147% of those impressions turn into an interaction. That is about 2.15% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 2.5 posts a day over the last 30 days, with activity on roughly 73% of days. Most posts go out around 04:00 UTC, and Friday is the busiest day of the week. Of the 70 posts sampled, 7% carry an image or video and 99% link out. The account's strongest tracked post pulled 43 interactions, about 4.3x its own typical post.

Measured over 70 original posts from a 30-day window, last computed on September 17, 2026.

Compared with accounts its own size

DEV Community's engagement rate beats 14% of the tracked X accounts closest to it in follower count (15,519 accounts, accounts of similar size (decile 9 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.

On engagement per impression rather than per follower it beats 9% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.

Where this sits in the catalog

At 0.003%, DEV Community sits above the 10th percentile of the 157,233 accounts in this comparison. That places it in the bottom 25% band, which runs below 0.022%.

p100.003%
p250.022%
p50 (median)0.128%
p750.604%
p902.32%
p9983.4%
Engagement rate as a share of followers, across the 157,233 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 26,048 times apart and a linear axis would flatten everything below the median into a single point.
Show the percentile table
Engagement rate percentiles
PercentileEngagement rate
10th percentile0.003%
25th percentile0.022%
50th percentile0.128%
75th percentile0.604%
90th percentile2.32%
99th percentile83.4%

This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built

Posting timing

This account posts most often around 04:00 UTC, and Friday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.

Engagement by hour posted, UTCTwenty-four bars, one per UTC hour. Each bar shows how posts published in that hour compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest hour: 04:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 04:00 UTC
Show engagement by hour posted, utc as a table
Engagement by hour posted, UTC
Hour (UTC)Vs author medianPosts
00:00 UTC-1%89K
01:00 UTC-2%90K
02:00 UTC-3%88K
03:00 UTC-4%94K
04:00 UTC-5%76K
05:00 UTC-4%75K
06:00 UTC-5%86K
07:00 UTC-5%93K
08:00 UTC-4%108K
09:00 UTC-4%124K
10:00 UTC-3%129K
11:00 UTC-3%141K
12:00 UTC-3%154K
13:00 UTC-3%167K
14:00 UTC-4%173K
15:00 UTC-2%176K
16:00 UTC-3%171K
17:00 UTC-3%159K
18:00 UTC-2%149K
19:00 UTC-2%141K
20:00 UTC-1%131K
21:00 UTC0%116K
22:00 UTC-2%100K
23:00 UTC-1%90K
Engagement by day of weekSeven bars, one per weekday, Sunday first. Each bar shows how posts published on that day compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest day: Friday.
SunMonTueWedThuFriSat
Above the authors' own mediansBelowScale: plus or minus 111%Busiest day: Friday
Show engagement by day of week as a table
Engagement by day of week
DayVs author medianPosts
Sunday+5%393K
Monday+1%483K
Tuesday-2%520K
Wednesday-3%472K
Thursday-2%430K
Friday-3%447K
Saturday+2%393K
See what moves engagement across the whole catalogWhat counts as a good engagement rate at this size

Formats this account uses

Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.

This account's posting mix compared with catalog-wide effects
FormatThis accountCatalog effect95% intervalAccounts behind it
Image or video7% of posts+111%+108% to +115%34K
Outbound link99% of posts-41%-42% to -40%32K
Typical length-no effect-2% to -1%42K
  • 7% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
  • 99% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts, so a large share of this account's output sits in the weakest bucket we measure.
  • Its average post runs 256 characters, which falls in the 180 - 280 characters band. Across the catalog, posts of 180 to 280 characters match the same accounts' other posts almost exactly.

These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.

Best tweets

  • Aug 24, 20264.3x their median

    Adding full text search to Postgres is a two line migration. Running it without surprises is not. This dev covers GIN write amplification, what to watch during a real load test, and why relevance needs a judged query set. { author: Libme } https://t.co/UuqFdTsUwL

    348108.9K viewsView on X
  • Sep 4, 20262.8x their median

    Our Weekend Challenge: Generosity Edition is live! 🟣 Build something in the spirit of generosity 🟣 $1,000 across FIVE winners 🟣 4 different ways to win Submissions due Sept 7 at 6:59 AM UTC https://t.co/giZioetTZB https://t.co/k354B432vr

    235006.3K viewsView on X
  • Sep 14, 20262.4x their median

    Multi-agent systems have a familiar problem: unpredictable black-box loops. This piece argues the fix looks like backend patterns already used for microservices, applied to agents instead of services. { author: Tilde A. Thurium + @GoogleAI } https://t.co/7QAfYupKtY

    184209.6K viewsView on X
  • Sep 9, 20262.3x their median

    Most of a custom Claude Code agent lineup turned out to be dead weight, quietly burning tokens on every request without ever running. The fix: two scripts that log invocations and flag anything unused for deletion. { author: @bokuwalily } https://t.co/jJtFntA3Ez

    124707.2K viewsView on X
  • Sep 6, 20262.2x their median

    Vector search finds what looks related. It cannot walk outage to vendor to customer to account owner. This dev wires Gemini to Neo4j over MCP so the agent checks the schema first, then picks its next hop. { author: Saurabh Mishra + @GoogleDevExpert } https://t.co/3baubMgmWa

    173208.5K viewsView on X
  • Sep 11, 20262.1x their median

    Congrats to @sizzlebopzz and @longlong1212121 the winners of our Frontend Challenge: Comfort Food Edition!! We had so many awesome submissions. Here a few of the highlights. 🄘 https://t.co/FB0DPkxklM

    143225.8K viewsView on X
  • Aug 21, 20262.1x their median

    Obsidian notes are plain markdown on disk, so any agent that reads a directory can read them. The trick is pointing it at one Map of Content file instead of a folder, and this dev covers what to leave out of the vault. { author: Shayan Araghi } https://t.co/bmglsdxIdF

    125408.0K viewsView on X
  • Sep 8, 20261.9x their median

    PostgreSQL's INCLUDE clause is usually explained as enabling index-only scans, but covering indexes existed before INCLUDE too. The real reason: unique indexes can't add columns to the key without changing what they enforce. { author: @FranckPachot } https://t.co/tUSNp4xJsW

    154008.1K viewsView on X
  • Sep 4, 20261.9x their median

    Code detectors flag clean, textbook code as machine written, punishing anyone who follows convention. This dev's answer is a local-first VS Code extension that records the process behind a codebase, not its final shape. { author: whaiman } https://t.co/ZmEr1hYE5H

    154006.8K viewsView on X
  • Aug 22, 20261.9x their median

    Anthropic signed the EU AI Act transparency code, and myths arrived faster than the docs. This dev separates what is confirmed about the imperceptible watermark from educated guesses, and why detection is not proof. { author: @SylwiaLask8977 } https://t.co/BwZC33hxVf

    123408.2K viewsView on X

Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.

Buy or sell Twitter (X) accounts - escrow-protected

PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.

Reading these numbers

A typical post picks up 10 interactions against 317K followers, an engagement rate of 0.003%. Measured over 70 original posts, its engagement rate beats 14% of 15,519 tracked accounts of a similar size. That is a reason to look at how the audience behaves - reply depth, saves, whether the followers are recent - rather than a conclusion about it on its own. Posts are seen about 6.8K times each, and 0.147% of those impressions turn into an interaction. That is about 2.15% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 2.5 posts a day over the last 30 days, with activity on roughly 73% of days. Most posts go out around 04:00 UTC, and Friday is the busiest day of the week. Of the 70 posts sampled, 7% carry an image or video and 99% link out. The account's strongest tracked post pulled 43 interactions, about 4.3x its own typical post.

What is DEV Community's engagement rate on X?
DEV Community (@ThePracticalDev) has an engagement rate of 0.003%, based on the median interactions across 70 original posts from the last 30 days against 316,586 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.003%, DEV Community sits above the 10th percentile of the 157,233 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
Does @ThePracticalDev have real engagement?
Its engagement rate beats 14% of the tracked X accounts closest to it in follower count (15,519 accounts), which puts it in the bottom quarter for its size group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
When does @ThePracticalDev post?
Most posts go out around 04:00 UTC, and Friday is its busiest day, at roughly 2.53 posts per day across the measured window.

Keep going