Data Science Dojo engagement report
@DataScienceDojo - 230K followers on X
Measured over 20 original posts from a 30-day window, last computed on September 30, 2026.
Engagement
A typical post picks up 8 interactions against 230K followers, an engagement rate of 0.004%. Measured over 20 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 3.6K times each, and 0.223% of those impressions turn into an interaction. That is about 1.56% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.67 post a day over the last 30 days, though only 37% of days saw any activity at all. Most posts go out around 18:00 UTC, and Wednesday is the busiest day of the week. Of the 20 posts sampled, 75% carry an image or video and 100% link out. The account's strongest tracked post pulled 419 interactions, about 52x its own typical post.
Measured over 20 original posts from a 30-day window, last computed on September 30, 2026.
Compared with accounts its own size
Data Science Dojo'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 14% 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.004%, Data Science Dojo sits above the 10th percentile of the 156,596 accounts in this comparison. That places it in the bottom 25% band, which runs below 0.022%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.003% |
| 25th percentile | 0.022% |
| 50th percentile | 0.127% |
| 75th percentile | 0.604% |
| 90th percentile | 2.32% |
| 99th percentile | 83.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 18:00 UTC, and Wednesday 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.
Show engagement by hour posted, utc as a table
| Hour (UTC) | Vs author median | Posts |
|---|---|---|
| 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 UTC | 0% | 116K |
| 22:00 UTC | -2% | 100K |
| 23:00 UTC | -1% | 90K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +5% | 393K |
| Monday | +1% | 483K |
| Tuesday | -2% | 520K |
| Wednesday | -3% | 472K |
| Thursday | -2% | 430K |
| Friday | -3% | 447K |
| Saturday | +2% | 393K |
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.
| Format | This account | Catalog effect | 95% interval | Accounts behind it |
|---|---|---|---|---|
| Image or video | 75% of posts | +111% | +108% to +115% | 34K |
| Outbound link | 100% of posts | -41% | -42% to -40% | 32K |
| Typical length | - | +15% | +14% to +16% | 32K |
- 75% 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.
- 100% 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 857 characters, which falls in the over 280 characters band. Across the catalog, posts over 280 characters run 15% above the same accounts' other posts.
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
- Jul 24, 202652x their median
š” The AI industry has a naming problem. Five terms in five years. ā¢ šš«šØš¦š©š šš§š š¢š§ššš«š¢š§š (2022): Crafting the instructions you give a model in one exchange. ā¢ ššØš§ššš±š šš§š š¢š§ššš«š¢š§š (2025): Managing everything the model knows beyond the prompt: retrieved documents, memory, tool definitions, session history. ā¢ ššš«š§šš¬š¬ šš§š š¢š§ššš«š¢š§š (š šš 2026): The constraints and gates that keep an agent in bounds. A good prompt won't stop an agent from rewriting your entire codebase if nothing architecturally prevents it. ā¢ ššØšØš© šš§š š¢š§ššš«š¢š§š (šš®š§š 2026): Designing the plan-execute-verify cycle an agent repeats, and deciding what triggers each step and what counts as done. ā¢ šš«šš©š” šš§š š¢š§ššš«š¢š§š (šš®š„š² 2026): Wiring multiple agent loops together through nodes, edges, and shared state, instead of relying on one agent to handle everything sequentially. Lay them out like this and the picture gets clearer. Prompt, context, and harness engineering are genuinely different layers of the same single-agent problem. Loop and graph engineering sit much closer together, a graph is just what happens when one loop isn't enough and you need several coordinating. And here's the part worth sitting with: harness to loop to graph is three renamed "eras" in about five months. That's a pace no other engineering discipline moves at, which says something about how much of this is new architecture versus new vocabulary. We found 6 frameworks that were already doing "graph engineering," nodes, edges, shared state and all, before the term existed. Full breakdown on the šš„šØš , link in the ššØš¦š¦šš§šš¬. #AIengineering #AgenticAI #LLMEngineering #AIagents #MultiAgentSystems #LangGraph
- Jul 27, 202614x their median
š¢ The retrieval step in a RAG system is only as good as the chunks feeding it ā and most teams don't think carefully about chunking until something breaks. The way you split your documents determines what your retrieval system can find, what your LLM actually sees, and whether the answer it generates reflects the full picture or just a fragment of it. Most people treat chunking as a one-time setup decision ā pick a size, move on. But every strategy makes a different tradeoff between how precisely a chunk can be retrieved and how much reasoning context it carries. Optimize for one without thinking about the other and you'll either get the right chunk with half the meaning, or a chunk rich enough to answer the question that never gets retrieved at all. There's no universal right answer here. There's only understanding what each approach actually does ā and picking the one that fits what your system needs to do. This carousel walks through 5 chunking strategies, what each one gets right, and where each one quietly breaks down. #RAG #LLM #AIEngineering #VectorSearch #AgenticAI #RetrievalAugmentedGeneration
- Jul 23, 20267.4x their median
šØ Cursor just launched šš®š«š¬šØš« ššØš®ššš« in early access, an automatic model-routing layer. Cursor says it delivers frontier-quality coding results at 60% lower cost than routing every request to Opus 4.8, with no measured quality drop in internal testing. The detail that matters is what triggered this: ⢠OpenAI rolled out hard spend limits across all API accounts the same week ⢠Model routing is becoming the default way teams control cost on high-volume coding and agent workloads, not a manual optimization ⢠Router picks a cheaper model automatically per request instead of leaving that choice to the developer, which only works if the routing logic reliably detects when a task actually needs the expensive model If you're running Cursor on a team plan, turn on Router in early access and compare your actual spend and output quality over a week before trusting the 60% number on your own codebase. We broke down how the Router classifier actually works, the real early-access savings range (30-50%, not just the 60% headline), and what to watch next. Full breakdown linked in comments. #CursorAI #ModelRouting #AICodingTools #DevProductivity #AIEngineering
- Jul 29, 20266.6x their median
šØ Five days. 40 hours. One ššš šš©š©š„š¢šššš¢šØš§ you'll build yourself. That's the shape of our next LLM Bootcamp, running August 24-28, 2026. We're not stopping at prompting basics: this goes into transformers and attention mechanisms, vector databases, fine-tuning, and the RAG challenges that trip up most production systems. By day five, you're evaluating your own šš šš§šš¬ and shipping a real build. 12,000+ alumni and 2,500+ companies have gone through this program. If you've been meaning to go from "I use LLMs" to "I can build with them," August is your window. Grab your seat before the cohort fills. Link in the comments! #LLMBootcamp #AgenticAI #RAGSystems #AIEngineering #FineTuning
- Jul 23, 20266.3x their median
šØ Five days. 40 hours. One ššš šš©š©š„š¢šššš¢šØš§ you'll build yourself. That's the shape of our next LLM Bootcamp, running August 24-28, 2026. We're not stopping at prompting basics: this goes into transformers and attention mechanisms, vector databases, fine-tuning, and the RAG challenges that trip up most production systems. By day five, you're evaluating your own šš šš§šš¬ and shipping a real build. 12,000+ alumni and 2,500+ companies have gone through this program. If you've been meaning to go from "I use LLMs" to "I can build with them," August is your window. Grab your seat before the cohort fills. Link in the comments! #LLMBootcamp #AgenticAI #RAGSystems #AIEngineering #FineTuning
- Jul 29, 20265.0x their median
LLM Wikis take a different approach to agent memory. Instead of just retrieving raw chunks like RAG (and then forgetting them), the agent actually curates what it learns: it reads new information, reconciles it against what it already knows, and rewrites its own knowledge into clean, current pages ā much like a human maintaining a living wiki. In this session, Izma Aziz, Senior Software Engineer - Generative AI and LLMs at Data Science Dojo, breaks down how LLM Wikis actually work ā and why they matter for agents that need to remember. Here's what we'll cover: š¹ What LLM Wikis are, and how an agent maintains its own knowledge base š¹ How they differ from RAG, file search, and chat memory š¹ Where they pay off ā fewer tokens, lower cost, cleaner knowledge š¹ How knowledge gets created and updated, in a live build š¹ What makes agent memory reliable in production If you're building or maintaining LLM-powered agents and want a real alternative to RAG for long-term memory, this one's for you. š August 5, 2026 | 1:00 PM PT Register here: https://t.co/YXfsSm8qKb #LLMWikis #AIAgents #AgentMemory #GenerativeAI #LLM #LangGraph #DeepAgents #RAG #AIEngineering #MachineLearning #ArtificialIntelligence
- Jun 30, 20264.4x their median
The July 14th cohort is coming up soon. 10 weeks. 12,000+ alumni. Spots are filling fast. The Agentic AI Bootcamp is back and it covers the full stack of what matters right now. Week 1, you're wrapping your head around how Transformers actually work. Week 3, you're building with LangChain and setting up your first vector database for a RAG pipeline. By week 5, you're not just prompting. You're engineering context and designing systems using Agentic design patterns used in production. Week 7 hits and you're implementing Model Context Protocol and learning how agents actually talk to each other. Week 10? You ship a multi-agent LLM application. From scratch. In 10 weeks. That's what the Agentic AI Bootcamp cohort starting July 14th looks like. 3 hours a week, structured to take you from foundations to deployment. Register now before it's too late: https://t.co/gOKkz5sjhv #agenticai #rag #aibootcamp #vectordatabases
- Sep 4, 20263.0x their median
Prompt injection isn't the only way an agent goes rogue. Sometimes it's just doing exactly what it was told, with permissions that were too broad to begin with. Join Dan Ndombe, Staff Developer Success Advocate at Docker, for a hands-on session on running LLM agents safely using Docker Sandboxes. We'll spin up a sandboxed agent runtime, give it a real task, then tighten the policy around it so it can only do what it's meant to do. In this session, you'll learn: - How Docker Sandboxes isolate an agent's filesystem, network, and process access from the host - How to hand a sandboxed agent a real task, end to end - How to read and tighten a sandbox policy: what to allow, what to block, and why - Common ways "sandboxed" agents leak permissions anyway - A reusable containment pattern for your own agent prototypes No prior Docker experience required. We'll build live and take questions. š Wednesday, September 16, 2026 | 11:00 AM ā 12:00 PM PT šļø Dan Ndombe, Staff Developer Success Advocate, Docker š Virtual š Register here: https://t.co/zceI23qOWX #AgenticAI #AIAgentSecurity #Docker #datasciencedojo
- Jul 22, 20263.0x their median
š” Getting an LLM to produce a coherent response in a demo takes an afternoon. Ā Getting it to behave consistently across edge cases, stay within cost, and not hallucinate on the inputs that matter ā that's where teams spend months they didn't plan for. Ā This carousel covers the 10 š¬š¤š¢š„š„š¬ that actually close that gap: from RAG pipelines and vector databases to fine-tuning with LoRA, evaluation frameworks like RAGAs and G-Eval, and agentic systems built on MCP. Ā Each one maps to a module in our ššš«š š ššš§š š®šš š ššØššš„š¬ ššØšØšššš¦š© ā 40 hours, in-person and online, starting August 24th. If you want to build LLM applications that hold up in production, this is the structured path to get there. Ā Link to the curriculum in the comments. #LLMBootcamp #LargeLanguageModels #AIEngineering #RAG #AgenticAI #LLMDevelopment
- Aug 19, 20262.9x their median
LLM Wikis: How AI Agents Build a Second Brain That Never Forgets https://t.co/0VF3GymTWT
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 8 interactions against 230K followers, an engagement rate of 0.004%. Measured over 20 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 3.6K times each, and 0.223% of those impressions turn into an interaction. That is about 1.56% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.67 post a day over the last 30 days, though only 37% of days saw any activity at all. Most posts go out around 18:00 UTC, and Wednesday is the busiest day of the week. Of the 20 posts sampled, 75% carry an image or video and 100% link out. The account's strongest tracked post pulled 419 interactions, about 52x its own typical post.
- What is Data Science Dojo's engagement rate on X?
- Data Science Dojo (@DataScienceDojo) has an engagement rate of 0.004%, based on the median interactions across 20 original posts from the last 30 days against 229,533 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.004%, Data Science Dojo sits above the 10th percentile of the 156,596 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 @DataScienceDojo 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 @DataScienceDojo post?
- Most posts go out around 18:00 UTC, and Wednesday is its busiest day, at roughly 0.67 posts per day across the measured window.