Boris Cherny engagement report
@bcherny - 566K followers on X
Measured over 2 original posts from a 30-day window, last computed on August 27, 2026.
Engagement
Early reading. We have captured 2 original posts for this account, below the 8 we require before treating a median as settled. The numbers above describe what we have seen so far, not a finished profile of the account.
A typical post picks up 4.5K interactions against 566K followers, an engagement rate of 0.806%. Posts are seen about 795K times each, and 0.569% of those impressions turn into an interaction. That is about 140.4% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.8 post a day over the last 30 days, though only 37% of days saw any activity at all. Most posts go out around 21:00 UTC, and Thursday is the busiest day of the week. Of the 2 posts sampled, 100% carry an image or video and 100% link out. The account's strongest tracked post pulled 24K interactions, about 5.3x its own typical post. Only 2 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.
Measured over 2 original posts from a 30-day window, last computed on August 27, 2026.
Where this sits in the catalog
At 0.806%, Boris Cherny sits above the 75th percentile of the 36,654 accounts in this comparison. That places it in the top 25% band, which runs 0.433% to 2.10%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.002% |
| 25th percentile | 0.012% |
| 50th percentile | 0.08% |
| 75th percentile | 0.433% |
| 90th percentile | 2.10% |
| 99th percentile | 160.5% |
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 21:00 UTC, and Thursday 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% | 51K |
| 01:00 UTC | -2% | 52K |
| 02:00 UTC | -3% | 50K |
| 03:00 UTC | -4% | 53K |
| 04:00 UTC | -6% | 43K |
| 05:00 UTC | -4% | 42K |
| 06:00 UTC | -4% | 48K |
| 07:00 UTC | -5% | 52K |
| 08:00 UTC | -4% | 61K |
| 09:00 UTC | -3% | 70K |
| 10:00 UTC | -2% | 72K |
| 11:00 UTC | -3% | 78K |
| 12:00 UTC | -2% | 86K |
| 13:00 UTC | -2% | 94K |
| 14:00 UTC | -4% | 97K |
| 15:00 UTC | -2% | 101K |
| 16:00 UTC | -3% | 98K |
| 17:00 UTC | -2% | 91K |
| 18:00 UTC | -1% | 85K |
| 19:00 UTC | -1% | 80K |
| 20:00 UTC | -1% | 74K |
| 21:00 UTC | -1% | 66K |
| 22:00 UTC | -1% | 57K |
| 23:00 UTC | -2% | 52K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +4% | 231K |
| Monday | 0% | 288K |
| Tuesday | -2% | 278K |
| Wednesday | -1% | 251K |
| Thursday | -1% | 245K |
| Friday | -3% | 253K |
| Saturday | +3% | 227K |
Best tweets
- Jun 28, 20265.3x their median
As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes: 1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship 2. Builder: quickly turns a prototype/idea into production-grade product/infra 3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance 4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit 5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS. A healthy team needs a mix of these, depending on the product: - A product that is new and pre-PMF needs people that are strong at 1+2+3 - A product that is growing and has found PMF needs 2+3+4 and some 5 - A product that has strong PMF needs 3+4+5 and some 2 Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
- Jul 8, 20262.9x their median
New in Claude Code: /checkup Run /checkup to: 1. Clean up unused skills/MCPs/plugins and save context 2. Dedup your local CLAUDE.md against the checked in CLAUDE.md 3. Break up root CLAUDE.md into nested CLAUDE.md's + skills 4. Turn off slow hooks 5. Update your Claude Code to the latest version 6. Enable auto mode by default 7. Pre-approve frequently denied read-only commands .. And a few other goodies. /checkup confirms with you before making any changes. Enjoy!
- Jul 17, 20262.6x their median
I talk to engineers at other companies every day and hear the same thing: one person is 10x'ing their output with Claude but the rest of the org hasn't caught up. Watching teams adopt AI, I keep seeing the same 4 steps. I mapped them out here: Steps of AI Adoption https://t.co/kQnRAUMKpP
- Jul 15, 20262.5x their median
Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things. I think many of these automations have become even more important now. This is true for a number of reasons. First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time. Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time! Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation. Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.
- Jun 29, 20262.4x their median
In the next version of Claude Code: subagents run in the background by default, so you can keep talking to Claude while your subagents work If you want your agent to run in the foreground, just tell Claude
- Jun 30, 20262.1x their median
Claude Desktop is now available on Linux (Ubuntu and Debian) in beta. Alongside the browser and terminal, you now get a first-class desktop experience with Claude Code, Claude Cowork, and chat on all paid plans. https://t.co/m0K9t198t4
- Aug 13, 2026
A weird experiment I've been trying the last few weeks is having Claude take over day-to-day maintenance of our apps. Seeing early signs of life that this might be possible. The setup is straightforward: we have a Slack channel called proj-claude-maintains-apps. In it, Claude Tag runs a bunch of daily routines across iOS, Android, Desktop, web, CLI, and Agent SDK: - Crash fuzzer: open the app in a simulator and tap around to find ways to crash it, then root cause and fix the crashes - Dup unifier: scans the codebase for similar-yet-slightly-divergent abstractions, and puts up PRs to unify them - Dead-code remover: removes statically unreachable code, and adds logging to suspected dead code to check if it's really dead and if so, remove it the next day - Abstraction police: fixes leaky abstractions - a bunch more.. Results have been surprisingly positive. Over the last few weeks, these routines have opened 388 PRs across our repos, 180 of which we merged after Claude Code Review + human review. We're now thinking about how to streamline this to make merging these kinds of mechanical changes easier. Claude generally gets these PRs right on the first shot, and if it doesn't, we ask Claude to tune its routines so it's better the next day. Sometimes it takes a few days of tuning. To try a similar workflow, ask Claude Code or Tag, or create some routines directly at https://t.co/Z70hStEBH6. A few of the actual prompts I used below. Has anyone experimented with similar workflows?
- Dec 29, 2025
I'm hearing from many folks across finance industry that Claude for Excel is blowing their minds. The agentic coding takeoff but for other fields is coming in 2026.
- Aug 7, 2026
turns out you can get indirect prompt injection to ~0 on unseen attacks if you stack enough layers (model training + input probes + a classifier checking intent). didn't expect that a year ago. auto mode is default in claude code as of next week https://t.co/7KLnIzf6y7 https://t.co/ow4jX2CMZW
- Jun 19, 2026
Cool way to use Claude Code: deciphering Linear A, a 3500 year old written language from Crete https://t.co/Aqd4ZG7Cum Hope this holds up in peer review! 🤞
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 X accounts - escrow-protected
PlayerSells is an escrow marketplace for X accounts. Every deal is protected, with no middleman risk.
Reading these numbers
A typical post picks up 4.5K interactions against 566K followers, an engagement rate of 0.806%. Posts are seen about 795K times each, and 0.569% of those impressions turn into an interaction. That is about 140.4% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.8 post a day over the last 30 days, though only 37% of days saw any activity at all. Most posts go out around 21:00 UTC, and Thursday is the busiest day of the week. Of the 2 posts sampled, 100% carry an image or video and 100% link out. The account's strongest tracked post pulled 24K interactions, about 5.3x its own typical post. Only 2 original posts have been captured so far, fewer than the 8 posts we want behind a median before treating it as settled. Read the figures above as an early measurement of this account, not as a finished profile of it.
- What is Boris Cherny's engagement rate on X?
- Boris Cherny (@bcherny) has an engagement rate of 0.806%, based on the median interactions across 2 original posts from the last 30 days against 565,861 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.806%, Boris Cherny sits above the 75th percentile of the 36,654 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 @bcherny have real engagement?
- There is not yet enough sample to rank this account against others of its size.
- When does @bcherny post?
- Most posts go out around 21:00 UTC, and Thursday is its busiest day, at roughly 0.8 posts per day across the measured window.