Addy Osmani (@addyosmani) X analytics
@addyosmani
Claude Code @anthropicai
@addyosmani has 427.2K followers, a median of 62.6K views per post and a 0.95% engagement rate.
Based on 30 recent original posts (high confidence). Updated October 21, 2026.
At a glance
Key stats
- Followers
- 427.2K427,222 followers on October 21, 2026
- Median views per post
- 62.6K
- Average views per post
- 162.4K
- Engagement rate (by views)
- 0.95%
- Original posts per week
- 4.8
- Average engagements per post
- 1,549
Engagement grade
Developing
This is near the lower benchmark range for accounts with 100K-1M followers.
Profile score
71/100
- Profile completeness100
- Audience shape100
- Engagement25
- Consistency100
- Positioning clarity30
Monetization
Estimated X creator earnings
$9–$22 in the last 30 days
From 1.8M views on @addyosmani's original posts in the last 30 days.
Rewards eligibility: likely
Rough estimate. X publishes no payout rate, so this assumes about $5–12 per 1M original-post impressions from reported creator payouts. Only Premium viewers’ impressions count, so real payouts can be much lower.
Free report
How does your account compare with @addyosmani?
Get the same report for your own account by email: engagement grade, median views, best times to post and estimated earnings.
Growth
Follower growth
Tracked by Xholic since July 30, 2026.
| Date | Followers | Change |
|---|---|---|
| Oct 21, 2026 | 427,222 | +296 |
| Oct 19, 2026 | 426,926 | +308 |
| Oct 18, 2026 | 426,618 | +18,962 |
| Jul 30, 2026 | 407,656 | – |
Timing
Best times to post
When @addyosmani's recent posts performed best (UTC).
- #1 slot
7:12 PM
Monday · UTC
- #2 slot
8:18 PM
Tuesday · UTC
- #3 slot
7:34 PM
Wednesday · UTC
What worked
Top recent posts
- 01
@addyosmani ·
At Anthropic, Claude now writes 80% of our code. Engineers ship 8x more code per quarter. Side effect: Tests grew 10x. CI jobs up 25x in 6 months. Here's what helped us scale: https://t.co/WOL2r60vAE
- 325Replies
- 367Reposts
- 5KLikes
- 790.6KViews
5.5x average engagementHas an imageMedium length (100-200 characters)Posted Mon 19:00 UTC - 02
@addyosmani ·
I've joined @AnthropicAI! I'll be working on Claude Code and making it better for developers who use it. Here's a little Fable & Three.js
Watch video- 745Replies
- 297Reposts
- 10.3KLikes
- 1.5MViews
3.6x average engagementHas a videoMedium length (100-200 characters)Posted Tue 06:00 UTC - 03
@addyosmani ·
Give your agent a way to verify its work. This can dramatically improve the quality of output. With this process in place, Claude Code was able to write 90%+ of its code itself. When generating software at a faster rate than you can review it, the bottleneck shifts to proving that it works. @bcherny and team invested enough in verification, we've been able to move fast while maintaining stability. Code reviews aren't going away, but you need to think of it differently. One human reading through line-by-line is no longer going to work as a gate, it needs to evolve into a multi-layered verification system, built with fast deterministic feedback loops for your agents. This is where e2e tests, feature maps (as @poteto has been advocating), property tests and multi-agent adversarial reviews come in. These all provide opportunities to catch errors early and fix them before things get out of hand. You don't have enough eyeballs for the amount of code being written so your focus needs to be on product intent, risk assessment and evaluating evidence rather than reviewing code. Delegate the code checking work to your automated tests, scale your approvals based on risk, and turn your test failures into living evaluations. This approach helps maintain speed without losing reliability. Let the agents do what they do best and let you focus on what makes you irreplaceable: judgement, direction, and ownership. We tried to capture how we handle code review and verification in this writeup. Hopefully it's helpful.
- 217Replies
- 172Reposts
- 2.5KLikes
- 181.9KViews
3.0x average engagementText onlyLong post (over 200 characters)Posted Sat 23:00 UTCQuote post - 04
@addyosmani ·
Reminder: Claude Code can test if a skill or plugin actually improves Claude's answers. > claude plugin eval init Tell Claude what a good result looks like in your plugin's folder and it writes the test cases for you. > run claude plugin eval .
Watch video- 100Replies
- 120Reposts
- 1.8KLikes
- 181.9KViews
2.2x average engagementHas a GIFLong post (over 200 characters)Posted Mon 06:00 UTC - 05
@addyosmani ·
Claude Opus 5.5 drew each frame of this animation in JavaScript. Here's "how browsers work" in 40 seconds.
Watch video- 137Replies
- 163Reposts
- 2.4KLikes
- 217.8KViews
2.1x average engagementHas a videoMedium length (100-200 characters)Posted Thu 06:00 UTC - 06
@addyosmani ·
To make your agent produce high-quality output, equip it with a way to check its work. Tests are part of that. Here are some of the ones I think are worth investing in. - Write end-to-end tests that simulate real user flows and act as the ground truth - Use property-based testing to specify what should never happen and generate thousands of test cases that attempt to break those constraints - If replacing a system, compare the old and new versions using randomly selected inputs - Require tests to run quickly and deterministically, which reinforces the agent to retry when the loop is slow or unreliable (the agent may learn to retry, not fix the problem) Example tests say what should happen; properties say what must not.
- 107Replies
- 93Reposts
- 1.2KLikes
- 61.4KViews
1.5x average engagementHas an imageLong post (over 200 characters)Posted Mon 06:00 UTC
Latest
Recent posts by Addy Osmani
The latest 30 original posts from @addyosmani, newest first, as of October 21, 2026. Replies and reposts aren't included.
@addyosmani ·
Give your agent a way to verify its work. This can dramatically improve the quality of output. With this process in place, Claude Code was able to write 90%+ of its code itself. When generating software at a faster rate than you can review it, the bottleneck shifts to proving that it works. @bcherny and team invested enough in verification, we've been able to move fast while maintaining stability. Code reviews aren't going away, but you need to think of it differently. One human reading through line-by-line is no longer going to work as a gate, it needs to evolve into a multi-layered verification system, built with fast deterministic feedback loops for your agents. This is where e2e tests, feature maps (as @poteto has been advocating), property tests and multi-agent adversarial reviews come in. These all provide opportunities to catch errors early and fix them before things get out of hand. You don't have enough eyeballs for the amount of code being written so your focus needs to…
- 217Replies
- 172Reposts
- 2.5KLikes
- 181.9KViews
@addyosmani ·
Agents write code "much better on average at scale" is right. The "at scale" part comes from verification. Agents make checking cheap. The stuff that made "Good Code" expensive (tests, benchmarks, specs, real e2e runs) is now a cheap thing you can ask an agent for. You can improve the checks. So our work is less "review every line" and more "build loops the agent can run itself". Give the agent a way to verify the work. That loop is where quality comes from. And make taste compound. When the agent gets something wrong, write it down (shared config, a hook, a test) so it doesn't happen twice. A human still owns what ships but now they're reviewing evidence and not just diffs.
- 91Replies
- 55Reposts
- 652Likes
- 52.9KViews
@addyosmani ·
Verification is one of the most important things for getting great results out of your agent. Clearly define "done" before code review starts. A reviewer, human or agent, asked to find bugs without this may still find something that could be improved. Give Claude checks it can run (bash commands, tests, clicking through the app in a browser) and have it pass that too before it says it's finished. When nothing blocks merge and ship.
- 92Replies
- 50Reposts
- 610Likes
- 54.7KViews
@addyosmani ·
"your edge right now is understanding the possibilities and being curious" Using AI for software engineering is now the default. The engineers I've seen who have the edge are ambitious and have been grinding with agents for years on the job at this point. It's a compounding effect. For teams still unsure or catching up, the smartest thing I can advise is to be even more ambitious and aggressively share what you learn with your peers. If you do all this work privately, only you benefit. If your team only gets to experiment with AI after hours, you've quietly told them using it doesn't count. Senior engineers should be the first to make this shift. Their decades of taste in system design and failure modes is the secret sauce that makes agent output good. They should direct their experience to building with agents better safety. Then show whats working to others to replicate.
- 74Replies
- 54Reposts
- 641Likes
- 40.5KViews
@addyosmani ·
Don't forget: Claude Max & Team now include monthly API credits. Max 5x: $100, Max 20x: $200 Great for building apps & agents via the API, Managed Agents or Agent SDK. We hope you'll enjoy Opus 5.5 there too.
- 73Replies
- 20Reposts
- 905Likes
- 85.1KViews
@addyosmani ·
Pro and Max users will soon have Claude Code Projects! I've been enjoying using them. You use a project when you have a stream of related work that outlasts one session. Claude coordinates it, runs each task as a parallel cloud thread and you set the instructions, repos and memory once instead of repeating them. You can also hand off a batch of tasks, walk away and come back to the Overview pane showing which threads finished, which PRs are ready and which need your answer. Check out @delba_oliveira's video for more!
- 81Replies
- 26Reposts
- 575Likes
- 63KViews
@addyosmani ·
Whether agents feel like liberation or loss depends on which joy of engineering you lean on most: making, knowing, or mattering. I've seen engineers say many conflicting things about agents: some are bubbling with excitement and for the first time ever, they feel like they're in an all-star lineup, while others mourn for the death of their craft, leaving them feeling hollow. I'm someone who works with agents every day, so I understand these sentiments. Rather than take sides, my hope is that I help you understand this in a more nuanced way. Too often we see two camps: people who love the joy of coding and people who love the joy of shipping. I think this is a gross oversimplification. Rather than asking you to pick a side, I want to ask you to reflect on the elements of your work that are the most nourishing to you. I think most of us have three sources of joy in our work, which we interweave in multiple ways: - The joy of making (or "flow"): the joy of molding things in our…
- 90Replies
- 44Reposts
- 451Likes
- 37.4KViews
@addyosmani ·
Claude Haiku 5.5 is out 🎉 It's a cheap, fast and very capable small model. ~75% cheaper to run than Haiku 4.5 with an adjustable effort setting. My team loves it as a subagent alongside Opus 5.5.
- 53Replies
- 34Reposts
- 652Likes
- 37.4KViews
@addyosmani ·
You need both taste and judgement. You need taste to know what is good, and you need judgement to understand the price of quality. If you ask a model for a component or migration plan, it will create a lot of options, very quickly. Most of those drafts seem OK. So once you have a collection of work that meets the basic criteria, you can no longer use taste to select between them. You must choose. I like to think of this as two filters. There is the taste, and there is the judgement. And I think a lot of people mix those up. The first filter is taste. Taste is the feeling for what makes a thing good. Taste is that feeling you get first, before you're able to put into words what is good or bad about something. You've had that experience where something is bad but you're not sure why, until you've worked it through and can describe it. "This user experience was really clumsy" or "that error message was really aggravating." Taste is built up by experience and practice. It comes from…
- 74Replies
- 89Reposts
- 642Likes
- 30.5KViews
@addyosmani ·
To make your agent produce high-quality output, equip it with a way to check its work. Tests are part of that. Here are some of the ones I think are worth investing in. - Write end-to-end tests that simulate real user flows and act as the ground truth - Use property-based testing to specify what should never happen and generate thousands of test cases that attempt to break those constraints - If replacing a system, compare the old and new versions using randomly selected inputs - Require tests to run quickly and deterministically, which reinforces the agent to retry when the loop is slow or unreliable (the agent may learn to retry, not fix the problem) Example tests say what should happen; properties say what must not.
- 107Replies
- 93Reposts
- 1.2KLikes
- 61.4KViews
Show all 30Show fewer
@addyosmani ·
"You should know" is a useful plugin for Claude Code that lets you know important info you might have missed. Enable with: /plugin enable cc-plugin-you-should-know@builtin Another great use of mods!
- 49Replies
- 28Reposts
- 658Likes
- 66.8KViews
@addyosmani ·
Introducing Claude Code mods! Customize how it looks and works just by prompting it. https://t.co/nWlECF9OY5 A mod is a small JS/TS file that runs in your session. Watch events, rewrite behavior or draw UI. Share it as a plugin with others. Make Claude Code your own.
- 58Replies
- 8Reposts
- 306Likes
- 40.9KViews
@addyosmani ·
We shipped https://t.co/RWIKTNo8qY! a new home for developers building with Claude. Already live: how we made the Claude web app 3x faster, how to be effective with Opus 5.5, automating eval hillclimbing with Claude and much more. Lots more tips and articles soon 🙏
- 84Replies
- 73Reposts
- 1.3KLikes
- 176.9KViews
@addyosmani ·
Glad Claude limits feel different! The lower Opus 5.5 price goes straight into your limits. They go about 25% further than Opus 5. Cache reads cost 60% less and output is generated 30% faster: https://t.co/sAByrMngAk
- 83Replies
- 24Reposts
- 1.2KLikes
- 99.5KViews
@addyosmani ·
Bias towards action. Act quickly to learn faster without being careless. When I'm building products, I try to default to the smallest responsible step that gives me feedback with some guardrails so that mistakes are cheap to fix and have limited blast radius. That's helped me ship to millions of users. I've seen a lot of people stall out on their ideas and its happened to me too. On side-projects, I would keep refining them long after they were good enough to try out - it just "needs one more feature", "to load one second faster" etc. But it's easier to reason about something once it’s real and people start using it. The folks I've seen have the most impact often weren't the smartest in the room. They shipped something small, noticed what broke and shipped a better version as soon as possible. Being wrong early was part of how they learned. Meanwhile there were so many people waiting for certainty that just continued waiting and didn’t ship.
- 38Replies
- 84Reposts
- 796Likes
- 35.4KViews
@addyosmani ·
Cloud sessions for Claude Code are now GA! Start a task, close your laptop and it keeps going. Get a one-time $100 credit on Pro or $250 on Max to celebrate. Your sessions spend it before falling back to normal plan use. Claim it: https://t.co/v69gDUaRIt Many of you have already been using cloud sessions and we hope you'll enjoy the extra credit.
- 34Replies
- 9Reposts
- 177Likes
- 37.5KViews
@addyosmani ·
Claude Opus 5.5 drew each frame of this animation in JavaScript. Here's "how browsers work" in 40 seconds.
Watch video- 137Replies
- 163Reposts
- 2.4KLikes
- 217.8KViews
@addyosmani ·
AI lets you try more ideas than you'll ever ship. Each one can teach you something. Combine what you learn and that's what ships. Ideally something of value to users.
- 29Replies
- 11Reposts
- 210Likes
- 25.6KViews
@addyosmani ·
Opus 5.5 is my new daily driver. Fable-level on most work, cheaper and faster than Opus 5 and Pro/Max/Team users just got a banked reset! Demo:
Watch video- 46Replies
- 10Reposts
- 598Likes
- 37.6KViews
@addyosmani ·
Introducing Claude Opus 5.5! 40% lower cost than Opus 5 with cache reads 60% cheaper. It performs at the level of Claude Fable 5.1 for most tasks. I celebrated with a pelican riding a bike in Three.js.
Watch video- 108Replies
- 88Reposts
- 2KLikes
- 419.5KViews
@addyosmani ·
Reminder: Claude Code can test if a skill or plugin actually improves Claude's answers. > claude plugin eval init Tell Claude what a good result looks like in your plugin's folder and it writes the test cases for you. > run claude plugin eval .
Watch video- 100Replies
- 120Reposts
- 1.8KLikes
- 181.9KViews
@addyosmani ·
"you are in the reputation-building business, and software is actually downstream of that." Great read if you've started something new and feel pressure to prove yourself. The advice: don't spiral. Be a reliable teammate first & the bigger work will follow.
- 22Replies
- 45Reposts
- 792Likes
- 72.8KViews
@addyosmani ·
Claude Code now supports AGENTS.md. We'll fallback to it if CLAUDE.md isn't specified. Hope this helps :)
- 88Replies
- 41Reposts
- 932Likes
- 103.7KViews
@addyosmani ·
Projects are rolling out in Claude Code today. A Project is an ongoing conversation that coordinates a stream of related work for you. You describe a goal, Claude splits it into threads, runs them in parallel in the cloud and keeps going after you close your laptop. Starting with select Pro and Max users on cloud sessions.
- 42Replies
- 18Reposts
- 322Likes
- 57.3KViews
@addyosmani ·
At Anthropic, Claude now writes 80% of our code. Engineers ship 8x more code per quarter. Side effect: Tests grew 10x. CI jobs up 25x in 6 months. Here's what helped us scale: https://t.co/WOL2r60vAE
- 325Replies
- 367Reposts
- 5KLikes
- 790.6KViews
@addyosmani ·
Get more out of your Fable usage by using Opus for subagents. Great tip!
- 67Replies
- 33Reposts
- 767Likes
- 113.7KViews
@addyosmani ·
How do you hold the bar on production agent code?: 1. Agree on the outcome and the constraints first. What does "done" look like? what must it not touch? is the simpler design is to refactor or reuse what you already have? Then let Claude cook. You do not need a long planning ritual on the latest models. You do need to reject a bad change before it becomes a PR. 2. Give Claude a way to check its work. Put the exact build, test, and lint commands in there. Turn the things you reject in review into skills: /verify, e2e, schema checks and so on. Run those before you open the PR. Use /code-review. I've said that quality now lives in the constraints you put around your agents and think this is worth spending time on. 3. Your job is the design and the bar. Blast radius decides how much you read. Throwaway code with a small blast radius can be a black box. Production code should have a higher bar than if a human wrote it, especially anything that touches money, auth, or user data.…
- 59Replies
- 21Reposts
- 322Likes
- 62.2KViews
@addyosmani ·
Tip: Claude Code has several skill-cleanup commands. Each answers a different question. /skill-doctor → which skills you use /skills, then t → what each costs /doctor → fixes setup + CLAUDE.md debt /context → what's in the window now /usage → what burns your limits
- 60Replies
- 66Reposts
- 747Likes
- 47.3KViews
@addyosmani ·
I've joined @AnthropicAI! I'll be working on Claude Code and making it better for developers who use it. Here's a little Fable & Three.js
Watch video- 745Replies
- 297Reposts
- 10.3KLikes
- 1.5MViews
@addyosmani ·
How I do code reviews these days: more code = more selective human review i.e. don't read all the code. 1. Every PR gets a multi-agent first pass. It should find bugs, verify them, rank by severity, suggest fixes. Approval stays a human call on anything that matters. 2. Low blast radius changes on less sensitive code (there's often a lot!) can skip a deep human review once that review is clean. This helps keep the explosion of PRs manageable. 3. Core / sensitive paths still need an owner and human sign-off. That's where you spend time: verification, constraints and earning trust in what the agents can safely cover. You want to keep recoverability. Agents do the first pass and humans cover blast radius. Great question from @GergelyOrosz!
- 81Replies
- 81Reposts
- 1KLikes
- 153KViews
Formats
Content mix
- Text only
- 47%
- With media
- 40%
- With links
- 5 posts
- With hashtags
- 0 posts
Creator style: High-reach broadcaster
See the full app
This creator report is one small part of Xholic
Click through a sample creator's account in the real app. No sign-up, nothing to install.
- Posts written in your voice and scheduled for your best hours
- Buyers found on 𝕏, with a reply drafted for each one
- Analytics that show which posts grow you
No sign-up or login needed · Takes about 2 minutes
Grow your own account
Want numbers like @addyosmani's?
Xholic writes posts in your voice, schedules them for the hours your audience is active, and tracks what's working every day.
$0 today · Card required · Cancel anytime
Live demo: no sign-up or login needed · takes about 2 minutes
Keep browsing
More in AI & developers
See all of AI & developers
Keep exploring
Free tools
- Compare Twitter AccountsPut two public accounts head to head and see who leads on views, engagement, grade and posting pace.
- Twitter Engagement Rate CalculatorCalculate engagement rate from your numbers or a public profile and grade it against your tier.
- X Monetization CalculatorChange the assumptions behind six X revenue models and compare gross revenue with direct contribution.
Guides
- How to Write a Tweet With an AI Tweet GeneratorTurn a rough idea into a tweet worth posting: write a specific prompt, pick a tone and length, compare three drafts and make the best one sound like you.
- How to Analyze Any X Profile and Read the ReportAnalyze any public X profile and read the report properly: how each metric is calculated, what is measured vs estimated, and three worked readings.
From the blog
- 10 X Analytics API Alternative Options for 2026Compare 10 X analytics API alternatives for 2026, from low-cost data providers and custom scrapers to enterprise listening platforms.
- Twitter API Examples: A Practical Guide for BuildersExplore real Twitter API examples with code, auth flows, rate limits, and patterns for posting, streaming, analytics, and growth workflows on X.
Best tweets on this topic
- Best tweets about AI CodingExplore the best tweets about AI coding, coding agents, AI developer tools, software workflows, and production lessons. Updated every two weeks.
- Best tweets about Google AI StudioDiscover the best tweets about Google AI Studio, covering Gemini API prototypes, prompting, structured output, model testing, and developer workflows.
- Best tweets about GitHub CopilotFind the best tweets about GitHub Copilot, from coding workflows and agent features to reviews, limitations, and developer productivity. Updated every two weeks.
About this data
- Analytics are inferred from public profile and recent post data. They do not include private impressions, profile visits, link clicks, or follower-source data.
- Deleted, protected, unavailable, or rate-limited posts may be missing from the sample.
- Stats come from public posts Xholic has stored, not private X Analytics. Xholic is not affiliated with X Corp or @addyosmani.
- Own this account and want it hidden? Email support@xholic.ai — we verify ownership and handle requests within 2 working days.